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 81BB546BAE for ; Fri, 18 Jul 2025 21:34:41 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7AF7740E31; Fri, 18 Jul 2025 21:34:41 +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 E3AC640E2D for ; Fri, 18 Jul 2025 21:34:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1752867279; 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=xU47PxOkU1fDV46v8O+Gz9JjpS6NDO+jhn5z5vPqvUw=; b=LbtA++JeXHWy6NRLiF5hxpnFa8pgYnOJuAf5JW82BakFL9pknAvEWNfCxIyvHY5UDiw79F IHQkSKHZcz9nxE2UQohKJjE2z3W4goBxqRqog5UOlMXJmC7FcNEfEpfb23hFF+bD+0L62f STSAkWJ529F4QfgPhx3FLTevnLJJ2NU= Received: from mx-prod-mc-04.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-584-wzrFUVFEM0Wo8KLlqhESaw-1; Fri, 18 Jul 2025 15:34:38 -0400 X-MC-Unique: wzrFUVFEM0Wo8KLlqhESaw-1 X-Mimecast-MFC-AGG-ID: wzrFUVFEM0Wo8KLlqhESaw_1752867277 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-04.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 287C919560AD; Fri, 18 Jul 2025 19:34:37 +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 C4A3918003FC; Fri, 18 Jul 2025 19:34:35 +0000 (UTC) From: Kevin Traynor To: Long Wu Cc: Chaoyong He , dpdk stable Subject: patch 'net/nfp: fix flow rule freeing' has been queued to stable release 24.11.3 Date: Fri, 18 Jul 2025 20:29:42 +0100 Message-ID: <20250718193247.1008129-48-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: g2kVRKIQcmbvaxl0NdEAojHUWLnc28v24e63xNoxE8k_1752867277 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/c0e26e76eca88e3098aacc429d3e3d3128face51 Thanks. Kevin --- >From c0e26e76eca88e3098aacc429d3e3d3128face51 Mon Sep 17 00:00:00 2001 From: Long Wu Date: Mon, 14 Apr 2025 14:02:26 +0800 Subject: [PATCH] net/nfp: fix flow rule freeing [ upstream commit 80209fe2a03b900e3b5e97ea98f487aec01adecc ] The flow number limit is stored in `priv->flow_limit` now, so the free index should be calculated based on it, or there will be coredump problem. Fixes: 66df893f2fef ("net/nfp: support different flow steering rules limit") Signed-off-by: Long Wu Reviewed-by: Chaoyong He --- drivers/net/nfp/nfp_net_flow.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/nfp/nfp_net_flow.c b/drivers/net/nfp/nfp_net_flow.c index 7f3fff2186..0e5003ebe3 100644 --- a/drivers/net/nfp/nfp_net_flow.c +++ b/drivers/net/nfp/nfp_net_flow.c @@ -129,5 +129,5 @@ nfp_net_flow_position_free(struct nfp_net_priv *priv, uint32_t index; - index = NFP_NET_FLOW_LIMIT - 1 - nfp_flow->position; + index = priv->flow_limit - 1 - nfp_flow->position; priv->flow_position[index] = false; -- 2.50.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-07-18 20:29:12.777852095 +0100 +++ 0048-net-nfp-fix-flow-rule-freeing.patch 2025-07-18 20:29:10.930907331 +0100 @@ -1 +1 @@ -From 80209fe2a03b900e3b5e97ea98f487aec01adecc Mon Sep 17 00:00:00 2001 +From c0e26e76eca88e3098aacc429d3e3d3128face51 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 80209fe2a03b900e3b5e97ea98f487aec01adecc ] + @@ -11 +12,0 @@ -Cc: stable@dpdk.org