From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1051] l2fwd-event: signal unsafe usage
Date: Mon, 11 Jul 2022 18:00:08 +0000 [thread overview]
Message-ID: <bug-1051-3@http.bugs.dpdk.org/> (raw)
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.
reply other threads:[~2022-07-11 18:00 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-1051-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 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).