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 5A2CE46BAE for ; Fri, 18 Jul 2025 21:34:16 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 53AF040E49; Fri, 18 Jul 2025 21:34:16 +0200 (CEST) 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 231AB40E4D for ; Fri, 18 Jul 2025 21:34:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1752867254; 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=SBeVtE4wj7t7Ll32kA+gA6fV1JZEK8bUKq7CCmAr3ic=; b=f3GMzfINVLB5mzXDyHqAFp0xtslXOmM5+ID9GKU++QCUjeEWT9G/9XD6w902lfmUbQW3Ja 4vweLnMcsgTGNkkYUa21W6YwQjS8iAbCdwDsu59TTXdbdb4GY27b6Wdjj2+TQmQ1aeXuRk ocKHSHROQCKzdyzqD2ZOc9pr0lLS4+w= 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-582-oqrGvT7ENg6Q6nSKHd6CIg-1; Fri, 18 Jul 2025 15:34:09 -0400 X-MC-Unique: oqrGvT7ENg6Q6nSKHd6CIg-1 X-Mimecast-MFC-AGG-ID: oqrGvT7ENg6Q6nSKHd6CIg_1752867248 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (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 770AB1800283; Fri, 18 Jul 2025 19:34:08 +0000 (UTC) Received: from rh.redhat.com (unknown [10.44.32.40]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 4CAE8180049D; Fri, 18 Jul 2025 19:34:06 +0000 (UTC) From: Kevin Traynor To: Gregory Etelson Cc: Viacheslav Ovsiienko , dpdk stable Subject: patch 'net/mlx5: fix mark action with shared Rx queue' has been queued to stable release 24.11.3 Date: Fri, 18 Jul 2025 20:29:28 +0100 Message-ID: <20250718193247.1008129-34-ktraynor@redhat.com> In-Reply-To: <20250718193247.1008129-1-ktraynor@redhat.com> References: <20250718193247.1008129-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: 2rZ_Jm-W2KYljfMOO8lp88eiTXkhLa5sN53aLEt7boQ_1752867248 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.3 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 07/23/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/312f28ad91235b287288066ba5afc78d166f14fd Thanks. Kevin --- >From 312f28ad91235b287288066ba5afc78d166f14fd Mon Sep 17 00:00:00 2001 From: Gregory Etelson Date: Wed, 14 May 2025 10:50:18 +0300 Subject: [PATCH] net/mlx5: fix mark action with shared Rx queue [ upstream commit 28eeca69eb1d9bebb0105e47c82885b0a8403654 ] Fix the assignment of the mark_flag in the shared Rx queue setup in mlx5_flow_rxq_dynf_set(). Previously, mark_flag was not set correctly in all cases, which could lead to incorrect flow mark action behavior when configuring shared Rx queues. Fixes: 2d8763432add ("net/mlx5: fix shared Rx queue data access race") Signed-off-by: Gregory Etelson Acked-by: Viacheslav Ovsiienko --- drivers/net/mlx5/mlx5_flow.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c index 61833c0dcb..f83ae1883d 100644 --- a/drivers/net/mlx5/mlx5_flow.c +++ b/drivers/net/mlx5/mlx5_flow.c @@ -1866,6 +1866,6 @@ mlx5_flow_rxq_dynf_set(struct rte_eth_dev *dev) data->flow_meta_port_mask = priv->sh->dv_meta_mask; } - data->mark_flag = mark_flag; } + data->mark_flag = mark_flag; } } -- 2.50.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-07-18 20:29:12.305498935 +0100 +++ 0034-net-mlx5-fix-mark-action-with-shared-Rx-queue.patch 2025-07-18 20:29:10.904907251 +0100 @@ -1 +1 @@ -From 28eeca69eb1d9bebb0105e47c82885b0a8403654 Mon Sep 17 00:00:00 2001 +From 312f28ad91235b287288066ba5afc78d166f14fd Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 28eeca69eb1d9bebb0105e47c82885b0a8403654 ] + @@ -12 +13,0 @@ -Cc: stable@dpdk.org @@ -21 +22 @@ -index 8696cc4e95..3d49a2d833 100644 +index 61833c0dcb..f83ae1883d 100644 @@ -24 +25 @@ -@@ -1867,6 +1867,6 @@ mlx5_flow_rxq_dynf_set(struct rte_eth_dev *dev) +@@ -1866,6 +1866,6 @@ mlx5_flow_rxq_dynf_set(struct rte_eth_dev *dev)