From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/vhost/virtio Bug 1682] [dpdk-25.03] vhost_virtio_fuzzing/tso_forward_pkt: testpmd cannot exit normally when test fuzz
Date: Tue, 25 Mar 2025 03:16:55 +0000 [thread overview]
Message-ID: <bug-1682-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3048 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1682
Bug ID: 1682
Summary: [dpdk-25.03] vhost_virtio_fuzzing/tso_forward_pkt:
testpmd cannot exit normally when test fuzz
Product: DPDK
Version: 25.03
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: vhost/virtio
Assignee: dev@dpdk.org
Reporter: songx.jiale@intel.com
Target Milestone: ---
Created attachment 305
--> https://bugs.dpdk.org/attachment.cgi?id=305&action=edit
dpdk fuzz test file
Environment
===========
DPDK version: 5f37ee9c859f3ce08ca4364f1d8c0e70ec33ac83 version: 25.03.0-rc2
OS: Red Hat Enterprise Linux 9.4/5.14.0-427.13.1.el9_4.x86_64
Compiler: clang version 17.0.6
Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz
NIC hardware: N/A
NIC firmware: N/A
Test Setup
Steps to reproduce
==================
1. create packet file(If the environment already has these packets, can skip
this step)
mkdir -p /tmp/fuzz/vhost_pcap
python3 pkt.py
2. Compile dpdk and fuzz
tar zxf fuzz.tar.gz
cp -r fuzz /root/dpdk/app/
sed -i "s/'test-sad',/'test-sad',\n 'fuzz',/g" app/meson.build
rm -rf x86_64-native-linuxapp-clang
CC=clang meson --werror -Denable_kmods=True -Dbuildtype=debug -Db_lundef=false
-Db_sanitize=address x86_64-native-linuxapp-clang
ninja -C x86_64-native-linuxapp-clang
3. create vhost
rm -rf /tmp/sock0
x86_64-native-linuxapp-clang/app/dpdk-fuzz /tmp/fuzz/vhost_pcap/ --
-ignore_remaining_args=1 -l 1 -n 4 --file-prefix=vhost --vdev
'net_vhost0,iface=/tmp/sock0,queues=4' -- --rxq=4 --txq=4 --txd=1024 --rxd=1024
RTE>>vhost_autotest
4. start testpmd with virtio device
x86_64-native-linuxapp-clang/app/dpdk-testpmd -l 1,2 -n 4
--file-prefix=virtio_26049_20250311133724 --no-pci
--vdev=net_virtio_user0,mac=00:01:02:03:04:05,path=/tmp/sock0,queues=4 -- -i
--rxq=4 --txq=4 --txd=1024 --rxd=1024
5. set csum fwd and start fwd
set fwd csum
start
show port stats all
note: Loop query the port status. when the bps of the port receiving and
transmitting packets is found to be 0, exit testpmd.
6. exit testpmd
quit
Results:
========
Unable to exit testpmd, will get stuck.
Expected Result:
================
Testpmd receives and sends packets normally and exits normally.
bad commit:
===========
commit 76730c7b9b5a35d1a74d45a08153a03bdb1b26f8
Author: Jie Hai <haijie1@huawei.com>
Date: Fri Feb 14 09:56:38 2025 +0800
app/testpmd: use packet type parsing API
1. Use rte_net_get_ptype() to parse packets instead.
2. Support TSO for packets with IPv6 extension header.
Signed-off-by: Jie Hai <haijie1@huawei.com>
lib/vhost/fd_man.c | 439 +++++++++++++++++------------------------------------
lib/vhost/fd_man.h | 5 +-
2 files changed, 144 insertions, 300 deletions
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5208 bytes --]
next reply other threads:[~2025-03-25 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 3:16 bugzilla [this message]
2025-03-25 4:25 ` [DPDK/vhost/virtio Bug 1682] [dpdk-25.03] vhost_virtio_fuzzing/tso_forward_pkt: testpmd cannot exit normally when test fuzz 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-1682-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.