* DPDK and signal safety
@ 2024-07-02 17:23 Stephen Hemminger
0 siblings, 0 replies; only message in thread
From: Stephen Hemminger @ 2024-07-02 17:23 UTC (permalink / raw)
To: dev
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-07-02 17:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-07-02 17:23 DPDK and signal safety Stephen Hemminger
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.