Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

[Michael Biebl]

Am 20.02.2018 um 12:40 schrieb Gert Wollny:
> However, while upstream is certainly correct that a kernel bug is the trigger of 
> the lockup, systemd should not hang on this, because if sending messages to systemd 
> can lock up the system then this is actually an attack vector for a DoS attack. 

How is this an attack vector for a DoS attack? Please elaborate


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180220/cb54364c/attachment-0002.sig>