https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #141 from Marc Burkhardt (marc@xxxxxxxxxxxxxxx) --- (In reply to jaapbuurman from comment #140) > (In reply to Marc Burkhardt from comment #137) > > (In reply to jaapbuurman from comment #135) > > > Doesn't the Linux kernel team have any procedures in place for when such > a > > > critical bug is found? There are many people running this "stable" 4.19 > > > branch, many of whom are unaware of this bug. Shouldn't the stable branch > > be > > > rolled back to the last known good version? Going back to 4.18 is > certainly > > > a better option, but people unaware of this bug might still be running > > 4.19. > > > > That would mean depublishing of the 4.19 release as a whole as nobody knows > > _what_ exactly to roll back. And if one would know, they would fix the bug > > instead. > > > > I cannot remember such a scenario/bug in the past... > > I know it sounds bad, but isn't depublishing 4.19 the best course of action > right now? There's probably a lot of people running 4.19 that are completely > unaware of this bug and might or might not run into this later. > > Data corruption issues are one of the worst, and should be addressed ASAP, > even if it means temporary depublishing the latest kernel, right? 4.18.20 is from Nov 21st and came with 4.19.3. It lacks 3 releases of fixes parallel to 4.19.6 due to 4.18 being EOL. 4.19 is out in the wild now. You cannot "get it back" ... And people are probably more aware of a new 4.19 release pushed by the distros than a rollback of the 4.19 release. -- You are receiving this mail because: You are watching the assignee of the bug.
