* [Bug 1051] l2fwd-event: signal unsafe usage
@ 2022-07-11 18:00 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2022-07-11 18:00 UTC (permalink / raw)
To: dev
https://bugs.dpdk.org/show_bug.cgi?id=1051
Bug ID: 1051
Summary: l2fwd-event: signal unsafe usage
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
The signal_handler in l2fwd-event uses several functions that are not
async-signal-safe.
The call to rte_mempool_lookup() in signal_handler could deadlock if
interrupted during another lookup.
Also updating variable in signal handler should use __atomic_store
This is not a bug found by inspection. In practice the code is safe.
But examples are used by users to build applications, should be following best
practices.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-07-11 18:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-11 18:00 [Bug 1051] l2fwd-event: signal unsafe usage bugzilla
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).