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 4BD0B46468 for ; Mon, 24 Mar 2025 17:18:43 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 41F3740BA5; Mon, 24 Mar 2025 17:18:43 +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 CAD9440A71 for ; Mon, 24 Mar 2025 17:18:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1742833121; 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=PC+Ztg4VupDtJgu/hF17WCMWs07gSnUFTeQa2nLZj7c=; b=ALpOYvCkOtc8YREShgg1qE5BIWaxpnJCVGTqrch6iFf2mV5yU88EP3T+EbKHg3mUgOKOmr SH92XZ89EUhCs2aa+LYk8IqvVGu9EqJ913C3r1gzdGpC1/ZAKm81X3Qxs44bQ6mPUcDj9h upcJeFbTt7TD56StU+yB3s/kqQ5e3Tw= Received: from mx-prod-mc-02.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-98-tIiugia8NNyK6eB2hZrNnA-1; Mon, 24 Mar 2025 12:18:39 -0400 X-MC-Unique: tIiugia8NNyK6eB2hZrNnA-1 X-Mimecast-MFC-AGG-ID: tIiugia8NNyK6eB2hZrNnA_1742833117 Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 6EA69196DF0C; Mon, 24 Mar 2025 16:18:37 +0000 (UTC) Received: from rh.redhat.com (unknown [10.44.32.16]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 3019330001A1; Mon, 24 Mar 2025 16:18:35 +0000 (UTC) From: Kevin Traynor To: Arkadiusz Kusztal Cc: dpdk stable Subject: patch 'common/qat: fix devargs parsing' has been queued to stable release 24.11.2 Date: Mon, 24 Mar 2025 16:16:32 +0000 Message-ID: <20250324161731.63950-25-ktraynor@redhat.com> In-Reply-To: <20250324161731.63950-1-ktraynor@redhat.com> References: <20250324161731.63950-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: LLqKVM4aqYU3nO2NsT9aHVey0I7bJRLHMLnYd1rL2W0_1742833117 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit content-type: text/plain; charset="US-ASCII"; x-default=true 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 Hi, FYI, your patch has been queued to stable release 24.11.2 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 03/28/25. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/kevintraynor/dpdk-stable This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable/commit/e189913951ecee123cdb09633a0af414d3bf126c Thanks. Kevin --- >From e189913951ecee123cdb09633a0af414d3bf126c Mon Sep 17 00:00:00 2001 From: Arkadiusz Kusztal Date: Tue, 11 Mar 2025 10:30:24 +0000 Subject: [PATCH] common/qat: fix devargs parsing [ upstream commit b5f561739d81ed248fee9c801db4cd84caffc5b2 ] The function `strlen` returns the size of the string without a terminating null-character, therefore a request to allocate memory space for a parsed argument is too small by 1. Fixes: 99ab2806687b ("common/qat: isolate parser arguments configuration") Signed-off-by: Arkadiusz Kusztal --- drivers/common/qat/qat_device.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/common/qat/qat_device.c b/drivers/common/qat/qat_device.c index bca88fd9bd..b582e3bf8b 100644 --- a/drivers/common/qat/qat_device.c +++ b/drivers/common/qat/qat_device.c @@ -230,4 +230,5 @@ qat_dev_parse_command_line(struct qat_pci_device *qat_dev, if (len == 0) return 0; + ++len; /* Allocate per-device command line */ qat_dev->command_line = rte_malloc(NULL, len, 0); -- 2.48.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-03-24 16:15:15.736973209 +0000 +++ 0025-common-qat-fix-devargs-parsing.patch 2025-03-24 16:15:14.857923766 +0000 @@ -1 +1 @@ -From b5f561739d81ed248fee9c801db4cd84caffc5b2 Mon Sep 17 00:00:00 2001 +From e189913951ecee123cdb09633a0af414d3bf126c Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit b5f561739d81ed248fee9c801db4cd84caffc5b2 ] + @@ -11 +12,0 @@ -Cc: stable@dpdk.org