3 ms·
It's worth noting that this is a case of Linus flying off the handle based on incomplete information. It was latter revealed that the bug which caused this whol
by magila 11y ago
It's worth noting that this is a case of Linus flying off the handle based on incomplete information. It was latter revealed that the bug which caused this whole spat on LKML had already been fixed in systemd, Kay Sievers just failed to communicate that in the bug opened by Borislav Petkov.
- felixgallo 11y agothat is not at all what happened. Here's Kay Sievers, defiantly posting after in his own words after the incident: https://plus.google.com/+KaySievers/posts/3cWXzYqB6MB https://plus.google.com/+KaySievers/posts/3cWXzYqB6MB
- magila 11y agoThere 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.
- gaius 11y agoThe fact that this is posted on Google+ and not LKML says it all really.
- digi_owl 11y agoThe place have become something of a second home for a lot of Linux related devs. One potential problem with that is that the poster is free to delete any and all comments made to his posts.
- dredmorbius 11y agoNB: 404 on that link.