From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D9E7141CEC for ; Mon, 20 Feb 2023 17:08:29 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D314C43095; Mon, 20 Feb 2023 17:08:29 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id A873643081 for ; Mon, 20 Feb 2023 17:08:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1676909307; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qx3cvQ91h6eO8kvM+5dg82SmHU1cXY7gfaBbKUaxNKM=; b=ayk0bYlydjCgZT098q4YVAOuQyrIyn8pm0G31A1zHMKZdNgXQJK3W0nmbc9DCH/ZzyISeh UnsCMjI8DBIJFZ7FTzb+gbJwoqqcjZ4PvJ8dGiRgnRqZeTLgnDH2RuqFOSQOMtLhVN9QCZ M/9NOiptCQhQQFRwGO5b2zRHvKVbu1A= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-94-xvHaRjrANHCzHaO6KBySHg-1; Mon, 20 Feb 2023 11:08:22 -0500 X-MC-Unique: xvHaRjrANHCzHaO6KBySHg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 27A0E299E773; Mon, 20 Feb 2023 16:08:20 +0000 (UTC) Received: from [10.39.208.21] (unknown [10.39.208.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A3AF640C1423; Mon, 20 Feb 2023 16:08:18 +0000 (UTC) Message-ID: <1be1bdef-ea29-e5ea-71a5-ddd7a95e0597@redhat.com> Date: Mon, 20 Feb 2023 17:08:16 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [PATCH v2 01/16] test/bbdev: fix seg fault for non supported HARQ len To: Hernan Vargas , dev@dpdk.org, gakhil@marvell.com, trix@redhat.com Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com, stable@dpdk.org References: <20230215170949.60569-1-hernan.vargas@intel.com> <20230215170949.60569-2-hernan.vargas@intel.com> From: Maxime Coquelin In-Reply-To: <20230215170949.60569-2-hernan.vargas@intel.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org On 2/15/23 18:09, Hernan Vargas wrote: > Fix segmentation fault happening in corner case in test-bbdev. > This fault could happen when running some specific vectors which size > are not supported by the PMD. > > Fixes: 335c11fd276 ("app/bbdev: support HARQ validation") > Cc: stable@dpdk.org > > Signed-off-by: Hernan Vargas > --- > app/test-bbdev/test_bbdev_perf.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/app/test-bbdev/test_bbdev_perf.c b/app/test-bbdev/test_bbdev_perf.c > index 45e1780df7..027f32cbf1 100644 > --- a/app/test-bbdev/test_bbdev_perf.c > +++ b/app/test-bbdev/test_bbdev_perf.c > @@ -84,7 +84,7 @@ > /* Increment for next code block in external HARQ memory */ > #define HARQ_INCR 32768 > /* Headroom for filler LLRs insertion in HARQ buffer */ > -#define FILLER_HEADROOM 1024 > +#define FILLER_HEADROOM 2048 > /* Constants from K0 computation from 3GPP 38.212 Table 5.4.2.1-2 */ > #define N_ZC_1 66 /* N = 66 Zc for BG 1 */ > #define N_ZC_2 50 /* N = 50 Zc for BG 2 */ > @@ -2111,9 +2111,9 @@ validate_op_harq_chain(struct rte_bbdev_op_data *op, > ops_ld->n_filler; > if (data_len > deRmOutSize) > data_len = deRmOutSize; > - if (data_len > orig_op->segments[i].length) > - data_len = orig_op->segments[i].length; > } > + if (data_len > orig_op->segments[i].length) > + data_len = orig_op->segments[i].length; > /* > * HARQ output can have minor differences > * due to integer representation and related scaling Reviewed-by: Maxime Coquelin Thanks, Maxime