4 ms·
There were two different issues at play: 1. A system hang due an assertion in journald spamming kmsg. 2. The question of whether systemd should be logging to
by magila 11y ago
There were two different issues at play:
1. A system hang due an assertion in journald spamming kmsg.
2. The question of whether systemd should be logging to kmsg or doing anything based on the "debug" kernel command line argument.
Linus got pissed because, based on Steven Rostedt's post to LKML and the referenced bug report, it looked like Kay was refusing to fix issue #1, but that bug had already been addressed and a fix committed to systemd. In the aftermath there was also a flamewar over issue #2, which is what Lennart is responding to in that G+ post.
- digi_owl 11y agoNote that going by the Torvalds email, this is far from the first time him and Sievers has been at odds.
- merb 11y ago1. i think that assumtion is right. I mean rate limiting stuff that comes from anywhere is needed. not cause of the fact that systemd does it. I mean if I could write a userspace tool that crashes the kernel.. is somewhat aweful.