From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: DPDK and signal safety
Date: Tue, 2 Jul 2024 10:23:04 -0700 [thread overview]
Message-ID: <20240702102304.76bd504a@hermes.local> (raw)
The recent CVE in OpenSSH related signal safety piqued my interest in
any possible issues in DPDK.
While reviewing:
- The use of SIGBUS in linux/eal_dev is problematic.
It is using not signal safe routines such as rte_spinlock and logging.
This was done as part of hotplug support.
- The use of SIGBUS in eal_memmalloc is ok, since it is limited in scope
and only while alloc_seg()
- Tap uses rt sig and is sigsafe since only updating flag.
- FPGA driver is catching SIGINT in update_flash.
it calls dev_info which is not sig safe.
SIGINT is not enough here, what about SIGTERM or SIGHUP?
And overriding application signals does not appear to be documented.
reply other threads:[~2024-07-02 17:23 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=20240702102304.76bd504a@hermes.local \
--to=stephen@networkplumber.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).