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 A1ED048B69 for ; Fri, 21 Nov 2025 12:23:03 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9B246402E6; Fri, 21 Nov 2025 12:23:03 +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 10500402E6 for ; Fri, 21 Nov 2025 12:23:01 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1763724181; 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=2Ixxvk9QtNB8dE2v/Xu45VNn0Podme0LjFxOtQ+tJ+M=; b=jN8PJyjESDDCBIoIPs6MfJKgdCzDi1jbgkqZoM3TjjLE+xIejNXm/bYJxuRA5cD9kJpz5q gBm9TqI9HGaDY++bTqtAea28eteA/9h8A7cDXthZNN66I7K4HfNPRj/KvDsldm0ZH0qncv LE1fisYoWhAyqU5lQJC/M/yUt5vTFGk= 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-589-qdn61q0yMCe4cOWYHiXG5w-1; Fri, 21 Nov 2025 06:22:58 -0500 X-MC-Unique: qdn61q0yMCe4cOWYHiXG5w-1 X-Mimecast-MFC-AGG-ID: qdn61q0yMCe4cOWYHiXG5w_1763724177 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 825441956080; Fri, 21 Nov 2025 11:22:57 +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 4BBD230044DC; Fri, 21 Nov 2025 11:22:56 +0000 (UTC) From: Kevin Traynor To: Jiawen Wu Cc: dpdk stable Subject: patch 'net/txgbe: fix FDIR rule raw relative for L3 packets' has been queued to stable release 24.11.4 Date: Fri, 21 Nov 2025 11:20:18 +0000 Message-ID: <20251121112128.485623-34-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: HDcFrHJ2SkvXxQJWYjnqlS5FccEXc2-o2yq1YbzxcMA_1763724177 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/ba28c5021f4a9c877b161b025b7d06c48aad3c55 Thanks. Kevin --- >From ba28c5021f4a9c877b161b025b7d06c48aad3c55 Mon Sep 17 00:00:00 2001 From: Jiawen Wu Date: Mon, 27 Oct 2025 11:15:37 +0800 Subject: [PATCH] net/txgbe: fix FDIR rule raw relative for L3 packets [ upstream commit f1cd458035da9066379c457d27488eeb7741af46 ] Hardware supports FDIR flex field base setting from start of MAC header, IP header, L4 header, L4 payload. So for IP packet which has no L4 header, it cannot match the raw bytes with relative offset start from L3 payload. And FDIR flex bytes rule cannot match L2 packets. Therefore, we will declare that the relative offset is only used for matching the L4 packets. Fixes: aa4974765499 ("net/txgbe: fix raw pattern match for FDIR rule") Signed-off-by: Jiawen Wu --- drivers/net/txgbe/txgbe_fdir.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/net/txgbe/txgbe_fdir.c b/drivers/net/txgbe/txgbe_fdir.c index 77d0cc4c30..8d181db33f 100644 --- a/drivers/net/txgbe/txgbe_fdir.c +++ b/drivers/net/txgbe/txgbe_fdir.c @@ -259,8 +259,5 @@ txgbe_fdir_get_flex_base(struct txgbe_fdir_rule *rule) return TXGBE_FDIRFLEXCFG_BASE_PAY; - if (rule->input.flow_type & TXGBE_ATR_L3TYPE_MASK) - return TXGBE_FDIRFLEXCFG_BASE_L3; - - return TXGBE_FDIRFLEXCFG_BASE_L2; + return TXGBE_FDIRFLEXCFG_BASE_L3; } -- 2.51.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-11-21 11:05:10.660252103 +0000 +++ 0034-net-txgbe-fix-FDIR-rule-raw-relative-for-L3-packets.patch 2025-11-21 11:05:09.425201007 +0000 @@ -1 +1 @@ -From f1cd458035da9066379c457d27488eeb7741af46 Mon Sep 17 00:00:00 2001 +From ba28c5021f4a9c877b161b025b7d06c48aad3c55 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit f1cd458035da9066379c457d27488eeb7741af46 ] + @@ -15 +16,0 @@ -Cc: stable@dpdk.org