DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chengwen Feng <fengchengwen@huawei.com>
To: <thomas@monjalon.net>, <honest.jiang@foxmail.com>
Cc: <dev@dpdk.org>, <liuyonglong@huawei.com>, <vattunuru@marvell.com>
Subject: [PATCH v4 11/14] app/dma-perf: fix segment fault with large size
Date: Mon, 20 Oct 2025 12:11:02 +0800	[thread overview]
Message-ID: <20251020041105.1590-12-fengchengwen@huawei.com> (raw)
In-Reply-To: <20251020041105.1590-1-fengchengwen@huawei.com>

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")
Cc: stable@dpdk.org

Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
---
 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 694ad25cbe..6643ccc95f 100644
--- a/app/test-dma-perf/benchmark.c
+++ b/app/test-dma-perf/benchmark.c
@@ -525,6 +525,11 @@ setup_memory_env(struct test_configure *cfg, uint32_t nr_buf,
 		return -1;
 	}
 
+	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,
 			0,
-- 
2.17.1


  parent reply	other threads:[~2025-10-20  4:12 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 10:54 [PATCH 0/9] bugfix and refactor of dma-perf Chengwen Feng
2025-08-11 10:54 ` [PATCH 1/9] app/dma-perf: fix use-after-free Chengwen Feng
2025-08-11 10:54 ` [PATCH 2/9] app/dma-perf: add global section for config file Chengwen Feng
2025-08-11 10:54 ` [PATCH 3/9] app/dma-perf: use argparse lib to parse argument Chengwen Feng
2025-08-11 10:54 ` [PATCH 4/9] app/dma-perf: refactor output csv Chengwen Feng
2025-08-11 10:54 ` [PATCH 5/9] app/dma-perf: support list DMA devices Chengwen Feng
2025-08-11 10:54 ` [PATCH 6/9] app/dma-perf: add more global config Chengwen Feng
2025-08-11 10:54 ` [PATCH 7/9] app/dma-perf: remove invalid or redundant field Chengwen Feng
2025-08-11 10:54 ` [PATCH 8/9] app/dma-perf: refactor load config function Chengwen Feng
2025-08-11 10:54 ` [PATCH 9/9] app/dma-perf: refactor benchmark function Chengwen Feng
2025-08-12  2:06 ` [PATCH 00/10] bugfix and refactor of dma-perf Chengwen Feng
2025-08-12  2:06   ` [PATCH 01/10] app/dma-perf: fix use-after-free Chengwen Feng
2025-08-12  2:07   ` [PATCH 02/10] app/dma-perf: add global section for config file Chengwen Feng
2025-08-12  2:07   ` [PATCH 03/10] app/dma-perf: use argparse lib to parse argument Chengwen Feng
2025-08-12  2:07   ` [PATCH 04/10] app/dma-perf: refactor output csv Chengwen Feng
2025-08-12  2:07   ` [PATCH 05/10] app/dma-perf: support list DMA devices Chengwen Feng
2025-08-12  2:07   ` [PATCH 06/10] app/dma-perf: add more global config Chengwen Feng
2025-08-12  2:07   ` [PATCH 07/10] app/dma-perf: remove invalid or redundant field Chengwen Feng
2025-08-12  2:07   ` [PATCH 08/10] app/dma-perf: refactor load config function Chengwen Feng
2025-08-12  2:07   ` [PATCH 09/10] app/dma-perf: refactor benchmark function Chengwen Feng
2025-08-12  2:07   ` [PATCH 10/10] app/dma-perf: support specific error info Chengwen Feng
2025-09-11 14:53   ` [EXTERNAL] [PATCH 00/10] bugfix and refactor of dma-perf Vamsi Krishna Attunuru
2025-09-17  3:33 ` [PATCH v2 " Chengwen Feng
2025-09-17  3:33   ` [PATCH v2 01/10] app/dma-perf: fix use-after-free Chengwen Feng
2025-09-17  3:33   ` [PATCH v2 02/10] app/dma-perf: add global section for config file Chengwen Feng
2025-09-17  3:33   ` [PATCH v2 03/10] app/dma-perf: use argparse lib to parse argument Chengwen Feng
2025-09-17  3:33   ` [PATCH v2 04/10] app/dma-perf: refactor output csv Chengwen Feng
2025-09-17  3:33   ` [PATCH v2 05/10] app/dma-perf: support list DMA devices Chengwen Feng
2025-09-17  3:33   ` [PATCH v2 06/10] app/dma-perf: add more global config Chengwen Feng
2025-09-17  3:33   ` [PATCH v2 07/10] app/dma-perf: remove invalid or redundant field Chengwen Feng
2025-09-17  3:33   ` [PATCH v2 08/10] app/dma-perf: refactor load config function Chengwen Feng
2025-09-17  3:33   ` [PATCH v2 09/10] app/dma-perf: refactor benchmark function Chengwen Feng
2025-09-17  3:33   ` [PATCH v2 10/10] app/dma-perf: support specific error info Chengwen Feng
2025-10-13  3:02 ` [PATCH v3 00/13] bugfix and refactor of dma-perf Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 01/13] app/dma-perf: fix use-after-free Chengwen Feng
2025-10-13  7:55     ` Bruce Richardson
2025-10-13  8:15       ` fengchengwen
2025-10-13  3:02   ` [PATCH v3 02/13] app/dma-perf: add global section for config file Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 03/13] app/dma-perf: use argparse lib to parse argument Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 04/13] app/dma-perf: refactor output csv Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 05/13] app/dma-perf: support list DMA devices Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 06/13] app/dma-perf: add more global config Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 07/13] app/dma-perf: remove invalid or redundant field Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 08/13] app/dma-perf: refactor load config function Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 09/13] app/dma-perf: refactor benchmark function Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 10/13] app/dma-perf: support specific error info Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 11/13] app/dma-perf: fix segment fault with large size Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 12/13] app/dma-perf: fix on-flight DMA when verify data Chengwen Feng
2025-10-13  3:02   ` [PATCH v3 13/13] app/dma-perf: fix wrong stage to stop dmadev Chengwen Feng
2025-10-20  4:10 ` [PATCH v4 00/14] bugfix and refactor of dma-perf Chengwen Feng
2025-10-20  4:10   ` [PATCH v4 01/14] app/dma-perf: fix use-after-free Chengwen Feng
2025-10-20  4:10   ` [PATCH v4 02/14] app/dma-perf: add global section for config file Chengwen Feng
2025-10-20  4:10   ` [PATCH v4 03/14] app/dma-perf: use argparse lib to parse argument Chengwen Feng
2025-10-20  4:10   ` [PATCH v4 04/14] app/dma-perf: refactor output csv Chengwen Feng
2025-10-20  4:10   ` [PATCH v4 05/14] app/dma-perf: support list DMA devices Chengwen Feng
2025-10-20  4:10   ` [PATCH v4 06/14] app/dma-perf: add more global config Chengwen Feng
2025-10-20  4:10   ` [PATCH v4 07/14] app/dma-perf: remove invalid or redundant field Chengwen Feng
2025-10-20  4:10   ` [PATCH v4 08/14] app/dma-perf: refactor load config function Chengwen Feng
2025-10-20  4:11   ` [PATCH v4 09/14] app/dma-perf: refactor benchmark function Chengwen Feng
2025-10-20  4:11   ` [PATCH v4 10/14] app/dma-perf: support specific error info Chengwen Feng
2025-10-20  4:11   ` Chengwen Feng [this message]
2025-10-20  4:11   ` [PATCH v4 12/14] app/dma-perf: fix on-flight DMA when verify data Chengwen Feng
2025-10-20  4:11   ` [PATCH v4 13/14] app/dma-perf: fix wrong stage to stop dmadev Chengwen Feng
2025-10-20  4:11   ` [PATCH v4 14/14] app/dma-perf: refactor benchmark function Chengwen Feng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251020041105.1590-12-fengchengwen@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=dev@dpdk.org \
    --cc=honest.jiang@foxmail.com \
    --cc=liuyonglong@huawei.com \
    --cc=thomas@monjalon.net \
    --cc=vattunuru@marvell.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).