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 6BD4148B69 for ; Fri, 21 Nov 2025 12:22:46 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 637D54026F; Fri, 21 Nov 2025 12:22:46 +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 B94A5402DB for ; Fri, 21 Nov 2025 12:22:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1763724165; 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=ja67u++qTDVe8wScJzEvnWrWK6EVLT6I3dt6n5x0SKw=; b=eZQR78mXih2QRaqoYMDnWgBjMWVhqNz+RpXBOqrbCMaMHhh/EmkVSRzvw3fTZ2ZGV3ZOMJ DTqi2GMKyDA1tuQbiw3zsL8pfqCDRVcYZt6rT2Qh1LcJ8YSCxpuUI2RGg/QtDHVPyO4g0l 2aUKBDhs4KM9lGyGlfQE0Deauv0+JCs= 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-487-nylA4U-gMdCb3wKnHOqKwA-1; Fri, 21 Nov 2025 06:22:44 -0500 X-MC-Unique: nylA4U-gMdCb3wKnHOqKwA-1 X-Mimecast-MFC-AGG-ID: nylA4U-gMdCb3wKnHOqKwA_1763724163 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 3937719560AF; Fri, 21 Nov 2025 11:22:43 +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 EE82D30044DB; Fri, 21 Nov 2025 11:22:41 +0000 (UTC) From: Kevin Traynor To: Jiawen Wu Cc: dpdk stable Subject: patch 'net/txgbe: fix VF Rx buffer size in config register' has been queued to stable release 24.11.4 Date: Fri, 21 Nov 2025 11:20:10 +0000 Message-ID: <20251121112128.485623-26-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: ohp0tFEkY_9QtCm5cCEgBAg01gn65GbPlIuJJUrChNc_1763724163 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/c6a87e4b41cf9a49c5ad84a045c89a399fb88679 Thanks. Kevin --- >From c6a87e4b41cf9a49c5ad84a045c89a399fb88679 Mon Sep 17 00:00:00 2001 From: Jiawen Wu Date: Mon, 27 Oct 2025 11:15:28 +0800 Subject: [PATCH] net/txgbe: fix VF Rx buffer size in config register [ upstream commit ee2bc2d16c6d1c59d8f5eae16a874866e3a60de7 ] Refer to commit 8a3ef4b89e6d ("net/txgbe: fix Rx buffer size in config register"). When round up buffer size to 1K, to configure the register, hardware will receive packets exceeding the buffer size in LRO mode. It will cause a segment fault in the receive function. Fixes: 92144bb36c6f ("net/txgbe: support VF Rx/Tx") Signed-off-by: Jiawen Wu --- drivers/net/txgbe/txgbe_rxtx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/txgbe/txgbe_rxtx.c b/drivers/net/txgbe/txgbe_rxtx.c index e2ac091dfe..30b49f7cc4 100644 --- a/drivers/net/txgbe/txgbe_rxtx.c +++ b/drivers/net/txgbe/txgbe_rxtx.c @@ -5140,5 +5140,5 @@ txgbevf_dev_rx_init(struct rte_eth_dev *dev) buf_size = (uint16_t)(rte_pktmbuf_data_room_size(rxq->mb_pool) - RTE_PKTMBUF_HEADROOM); - buf_size = ROUND_UP(buf_size, 1 << 10); + buf_size = ROUND_DOWN(buf_size, 1 << 10); srrctl |= TXGBE_RXCFG_PKTLEN(buf_size); -- 2.51.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-11-21 11:05:10.427096745 +0000 +++ 0026-net-txgbe-fix-VF-Rx-buffer-size-in-config-register.patch 2025-11-21 11:05:09.410200943 +0000 @@ -1 +1 @@ -From ee2bc2d16c6d1c59d8f5eae16a874866e3a60de7 Mon Sep 17 00:00:00 2001 +From c6a87e4b41cf9a49c5ad84a045c89a399fb88679 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit ee2bc2d16c6d1c59d8f5eae16a874866e3a60de7 ] + @@ -14 +15,0 @@ -Cc: stable@dpdk.org @@ -22 +23 @@ -index d77db1efa2..a3472bcf34 100644 +index e2ac091dfe..30b49f7cc4 100644 @@ -25 +26 @@ -@@ -5257,5 +5257,5 @@ txgbevf_dev_rx_init(struct rte_eth_dev *dev) +@@ -5140,5 +5140,5 @@ txgbevf_dev_rx_init(struct rte_eth_dev *dev)