From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/testpmd Bug 1834] [dpdk-25.11-rc2] Segmentation fault in Rx offload testcase
Date: Wed, 19 Nov 2025 07:54:57 +0000 [thread overview]
Message-ID: <bug-1834-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1834
Bug ID: 1834
Summary: [dpdk-25.11-rc2] Segmentation fault in Rx offload
testcase
Product: DPDK
Version: unspecified
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: jiawenwu@trustnetic.com
Target Milestone: ---
There is a bug introduced by:
Commit 066f3d9cc21c ("ethdev: remove callback checks from fast path")
In test case 139.4 <Rx offload per-port setting in command-line>, testpmd set
fwd csum, and only enable Rx csum offload. Meanwhile, driver like txgbe set
'dev->tx_pkt_prepare = NULL' since Tx offload is disabled. Thus
rte_eth_tx_prepare() calls null pointer cause segmentation fault in
pkt_burst_checksum_forward(), bacause NULL check was removed.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2025-11-19 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 7:54 bugzilla [this message]
2026-02-17 22:03 ` [DPDK/testpmd Bug 1834] [dpdk-25.11-rc2] Segmentation fault in Rx offload testcase bugzilla
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=bug-1834-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.