[svlug] (forw) [DNG] Linux system can be brought down by sending SIGILL to Systemd
id at joeyh.name
Sat May 25 09:36:29 PDT 2019
Which is better, an init that receives an accidental ILL signal due to
the root user's error and ceases running, or an init that receives an ILL
due to actually trying to run an instruction that the CPU does not
support and ignores the problem and continues running?
The answer to that is perhaps less clear-cut than Martin Steigerwald would
have you believe. Bear in mind that in the second case the init has no
idea what state the CPU is in after the ILL. See also mozilla's old
behavior of catching and ignoring SEGV.
I do wonder if systemd is doing more work in its signal handler than
is wise and has a re-entrancy problem that these repeated
signals are sometimes triggering.
see shy jo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 833 bytes
Desc: not available
Url : http://lists.svlug.org/archives/svlug/attachments/20190525/dc4d09a4/attachment.bin
More information about the svlug