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 DD45448B69 for ; Fri, 21 Nov 2025 12:22:06 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D49B8402D4; Fri, 21 Nov 2025 12:22:06 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 62CF04026F for ; Fri, 21 Nov 2025 12:22:05 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1763724125; 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=sa3vIWggqIGIGM5K46sI89eN8ogbcjXDvvr2pNPkUtw=; b=SabD4yPxyAk5+AdVJHMNA9Tr2TlwRj01Q4EZOi0KfbQ4rTjpJanjwud3wxc3UZTs4pQwvo 6QgzdkdeuJna4E6r9VjAWkvYLVTJdGEXvGSjAGG0e75SuPqzmCTaUhFjfs1i/0w6XXpEWb 1PovvdxlS5ewrxrDBHAo9B1/xqZ8mgA= Received: from mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-651-6NkveTtYNk6rz3xc9ZyZVQ-1; Fri, 21 Nov 2025 06:22:01 -0500 X-MC-Unique: 6NkveTtYNk6rz3xc9ZyZVQ-1 X-Mimecast-MFC-AGG-ID: 6NkveTtYNk6rz3xc9ZyZVQ_1763724120 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-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 7D34C180034A; Fri, 21 Nov 2025 11:22:00 +0000 (UTC) Received: from rh.redhat.com (unknown [10.42.28.165]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id D39BA30044DC; Fri, 21 Nov 2025 11:21:58 +0000 (UTC) From: Kevin Traynor To: Anatoly Burakov Cc: Nipun Gupta , dpdk stable Subject: patch 'bus/cdx: fix device name in probing error message' has been queued to stable release 24.11.4 Date: Fri, 21 Nov 2025 11:19:47 +0000 Message-ID: <20251121112128.485623-3-ktraynor@redhat.com> In-Reply-To: <20251121112128.485623-1-ktraynor@redhat.com> References: <20251121112128.485623-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: sasorYgeLTOGfpMhFU9qReWjMcpgcFoswITdv7AGZ6I_1763724120 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.4 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 11/26/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/5c49a2b766745e6a25ccc07873a914bb00e0a581 Thanks. Kevin --- >From 5c49a2b766745e6a25ccc07873a914bb00e0a581 Mon Sep 17 00:00:00 2001 From: Anatoly Burakov Date: Fri, 24 Oct 2025 10:53:09 +0100 Subject: [PATCH] bus/cdx: fix device name in probing error message [ upstream commit ebd507b220b58ff8e2e87d1c2fce51cb1d4420d1 ] The variable cdx_addr is a stack-allocated zero-initialized char array, but it is never used anywhere, except as part of error message out. The intention is to display device name, so fix the code to reflect that. Fixes: 45ef232af515 ("bus/cdx: introduce AMD CDX bus") Signed-off-by: Anatoly Burakov Acked-by: Nipun Gupta --- drivers/bus/cdx/cdx_vfio.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/bus/cdx/cdx_vfio.c b/drivers/bus/cdx/cdx_vfio.c index 664f267471..2c224bfef0 100644 --- a/drivers/bus/cdx/cdx_vfio.c +++ b/drivers/bus/cdx/cdx_vfio.c @@ -386,5 +386,4 @@ cdx_vfio_map_resource_primary(struct rte_cdx_device *dev) { struct vfio_device_info device_info = { .argsz = sizeof(device_info) }; - char cdx_addr[PATH_MAX] = {0}; static void *cdx_map_addr; struct mapped_cdx_resource *vfio_res = NULL; @@ -452,5 +451,5 @@ cdx_vfio_map_resource_primary(struct rte_cdx_device *dev) if (ret < 0) { CDX_BUS_ERR("%s mapping region %i failed: %s", - cdx_addr, i, strerror(errno)); + dev_name, i, strerror(errno)); free(reg); goto err_vfio_res; -- 2.51.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-11-21 11:05:09.750527575 +0000 +++ 0003-bus-cdx-fix-device-name-in-probing-error-message.patch 2025-11-21 11:05:09.358200721 +0000 @@ -1 +1 @@ -From ebd507b220b58ff8e2e87d1c2fce51cb1d4420d1 Mon Sep 17 00:00:00 2001 +From 5c49a2b766745e6a25ccc07873a914bb00e0a581 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit ebd507b220b58ff8e2e87d1c2fce51cb1d4420d1 ] + @@ -11 +12,0 @@ -Cc: stable@dpdk.org @@ -20 +21 @@ -index c03bc01df7..a3cf53b6a6 100644 +index 664f267471..2c224bfef0 100644 @@ -23 +24 @@ -@@ -390,5 +390,4 @@ cdx_vfio_map_resource_primary(struct rte_cdx_device *dev) +@@ -386,5 +386,4 @@ cdx_vfio_map_resource_primary(struct rte_cdx_device *dev) @@ -29 +30 @@ -@@ -456,5 +455,5 @@ cdx_vfio_map_resource_primary(struct rte_cdx_device *dev) +@@ -452,5 +451,5 @@ cdx_vfio_map_resource_primary(struct rte_cdx_device *dev)