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 B7AD348B69 for ; Fri, 21 Nov 2025 12:22:34 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B13BF4026F; Fri, 21 Nov 2025 12:22:34 +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 67266402DB for ; Fri, 21 Nov 2025 12:22:33 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1763724153; 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=iwBHlM1iIFJaR84eGSEFt0Ydd83iOiL8D40wZBusgT0=; b=iOE2r1bLwkRD3nVOap7nDzXXGE3+FXXgxu8zam1AtHQ2TxRUXJypzPNvgYmaNqHRTVpDQa PUoBXHIxMlvDikEd7+KZnTNVnty9TUpKQerJwobUSyLzuZTJ1BtKDlnmEjgrVVB71U9SwB dqITo6jYYxJ7ka5Dw6PgpG9cVpRz+Qs= 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-389-Bn22DvyfOnelNiX1E71TSA-1; Fri, 21 Nov 2025 06:22:31 -0500 X-MC-Unique: Bn22DvyfOnelNiX1E71TSA-1 X-Mimecast-MFC-AGG-ID: Bn22DvyfOnelNiX1E71TSA_1763724150 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 88F4D1956096; Fri, 21 Nov 2025 11:22:30 +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 8C1CA30044DB; Fri, 21 Nov 2025 11:22:29 +0000 (UTC) From: Kevin Traynor To: Chengwen Feng Cc: dpdk stable Subject: patch 'app/dma-perf: check buffer size' has been queued to stable release 24.11.4 Date: Fri, 21 Nov 2025 11:20:03 +0000 Message-ID: <20251121112128.485623-19-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: f-0UoMBBjCoY7g8d-PP1G6nIwC8q3SGlk1IxDnshoCc_1763724150 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/5694265ad26746ac10a050e299dcfbcbfb5936ca Thanks. Kevin --- >From 5694265ad26746ac10a050e299dcfbcbfb5936ca Mon Sep 17 00:00:00 2001 From: Chengwen Feng Date: Mon, 20 Oct 2025 12:11:02 +0800 Subject: [PATCH] app/dma-perf: check buffer size [ upstream commit 12b050defa729b0edf416e25ddf16203bcb176e2 ] When the buf-size is too large, the test will show: Case process killed by signal 11 The root cause is that rte_pktmbuf_pool_create() will truncate the buf-size to uint16 type. This commit add a friendly error trace when encounter such case. Fixes: 623dc9364dc6 ("app/dma-perf: introduce DMA performance test") Signed-off-by: Chengwen Feng --- app/test-dma-perf/benchmark.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/app/test-dma-perf/benchmark.c b/app/test-dma-perf/benchmark.c index 6d617ea200..c08c5c8dc6 100644 --- a/app/test-dma-perf/benchmark.c +++ b/app/test-dma-perf/benchmark.c @@ -459,4 +459,9 @@ setup_memory_env(struct test_configure *cfg, } + if (buf_size > UINT16_MAX) { + PRINT_ERR("Error: Invalid buf size: %u\n", cur_buf_size); + return -1; + } + src_pool = rte_pktmbuf_pool_create("Benchmark_DMA_SRC", nr_buf, -- 2.51.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-11-21 11:05:10.216489487 +0000 +++ 0019-app-dma-perf-check-buffer-size.patch 2025-11-21 11:05:09.391068720 +0000 @@ -1 +1 @@ -From 12b050defa729b0edf416e25ddf16203bcb176e2 Mon Sep 17 00:00:00 2001 +From 5694265ad26746ac10a050e299dcfbcbfb5936ca Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 12b050defa729b0edf416e25ddf16203bcb176e2 ] + @@ -16 +17,0 @@ -Cc: stable@dpdk.org @@ -24 +25 @@ -index 694ad25cbe..6643ccc95f 100644 +index 6d617ea200..c08c5c8dc6 100644 @@ -27 +28 @@ -@@ -526,4 +526,9 @@ setup_memory_env(struct test_configure *cfg, uint32_t nr_buf, +@@ -459,4 +459,9 @@ setup_memory_env(struct test_configure *cfg,