From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 2073] pdump leaves behind pcap vdev
Date: Sat, 24 Oct 2026 22:22:13 +0000 [thread overview]
Message-ID: <bug-2073-3@https.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=2073
Bug ID: 2073
Summary: pdump leaves behind pcap vdev
Product: DPDK
Version: 26.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Noticed when running different capture commands for benchmark.
I was running pdump first and it makes a vdev (pcap) to send data to file.
But when it exits (by interrupt) it leaves that vdev behind.
Later runs work ok, just see log messages about uncontrollable vdev.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-10-24 22:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-2073-3@https.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.