From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 382] rte_eth: rx/tx callbacks invoked without lock protection
Date: Mon, 11 Aug 2025 20:41:29 +0000 [thread overview]
Message-ID: <bug-382-3-FF6mh7oq6d@https.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-382-3@https.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=382
Stephen Hemminger (stephen@networkplumber.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Stephen Hemminger (stephen@networkplumber.org) ---
Dumpcap (and pdump) do unregister.
The data is rxtx callback data is static and local to the process so it is
safe.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2665 bytes --]
parent reply other threads:[~2025-08-11 20:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-382-3@https.bugs.dpdk.org/>]
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-382-3-FF6mh7oq6d@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.