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 D450746468 for ; Mon, 24 Mar 2025 17:18:04 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C985640DD5; Mon, 24 Mar 2025 17:18:04 +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 7B30640A71 for ; Mon, 24 Mar 2025 17:18:03 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1742833083; 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=ki0gtms7B1alxgUbaDYr2WQlTsp2lMLCn+KPCHh8guw=; b=TI5/8VZ23p9QsbWD6KC4lVUx9loBTDtfcutz9J9EAjZng7qZpoIJzY+xLsAJjBob1uUxDa TpkmNnIVrbBvpjNTEoEsCfx4A4VDpaYMlyOq9iddc/VRIwNW61dufPWHTwfNUTa0LBHhJS UA/ljZgjkWdr7aXU84q0IVAdvY1/hQk= Received: from mx-prod-mc-05.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-652-I6Lm2t-xOMe3A3VJhSPR2Q-1; Mon, 24 Mar 2025 12:18:01 -0400 X-MC-Unique: I6Lm2t-xOMe3A3VJhSPR2Q-1 X-Mimecast-MFC-AGG-ID: I6Lm2t-xOMe3A3VJhSPR2Q_1742833080 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-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 8CE041933B6C; Mon, 24 Mar 2025 16:18:00 +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 E1B1330001A1; Mon, 24 Mar 2025 16:17:58 +0000 (UTC) From: Kevin Traynor To: Maayan Kashani Cc: Dariusz Sosnowski , dpdk stable Subject: patch 'net/mlx5: fix LACP packet handling in isolated mode' has been queued to stable release 24.11.2 Date: Mon, 24 Mar 2025 16:16:16 +0000 Message-ID: <20250324161731.63950-9-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: 7vhJu96YwJw3XXu1F-dbg9OZyBf3wlIylxyfXmsDmGo_1742833080 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/a41da12914a83f039a1b1d38783a1408e3cfd951 Thanks. Kevin --- >From a41da12914a83f039a1b1d38783a1408e3cfd951 Mon Sep 17 00:00:00 2001 From: Maayan Kashani Date: Thu, 27 Feb 2025 12:20:44 +0200 Subject: [PATCH] net/mlx5: fix LACP packet handling in isolated mode [ upstream commit d15d74fc4b22cf7f09194f7d4de8d8ee03ca63a6 ] Fix an issue with handling LACP packets when the device is operating in isolated mode. The problem was caused by an incorrectly positioned isolated mode check, which led to improper processing of these packets. This ensures that LACP packets are handled correctly in compliance with the expected behavior. Fixes: 87e4384d2662 ("net/mlx5: fix condition of LACP miss flow") Signed-off-by: Maayan Kashani Acked-by: Dariusz Sosnowski --- drivers/net/mlx5/mlx5_trigger.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/mlx5/mlx5_trigger.c b/drivers/net/mlx5/mlx5_trigger.c index 79b3d4d982..4ee44e9165 100644 --- a/drivers/net/mlx5/mlx5_trigger.c +++ b/drivers/net/mlx5/mlx5_trigger.c @@ -1534,9 +1534,9 @@ mlx5_traffic_enable_hws(struct rte_eth_dev *dev) DRV_LOG(INFO, "port %u FDB default rule is disabled", dev->data->port_id); } - if (priv->isolated) - return 0; if (!priv->sh->config.lacp_by_user && priv->pf_bond >= 0 && priv->master) if (mlx5_flow_hw_lacp_rx_flow(dev)) goto error; + if (priv->isolated) + return 0; if (dev->data->promiscuous) flags |= MLX5_CTRL_PROMISCUOUS; -- 2.48.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-03-24 16:15:15.136673738 +0000 +++ 0009-net-mlx5-fix-LACP-packet-handling-in-isolated-mode.patch 2025-03-24 16:15:14.725735398 +0000 @@ -1 +1 @@ -From d15d74fc4b22cf7f09194f7d4de8d8ee03ca63a6 Mon Sep 17 00:00:00 2001 +From a41da12914a83f039a1b1d38783a1408e3cfd951 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit d15d74fc4b22cf7f09194f7d4de8d8ee03ca63a6 ] + @@ -14 +15,0 @@ -Cc: stable@dpdk.org