Recent searches
Search options
Administered by:
I fully understand why #Linux mainline developers do not have to care about stable #kernel maintenance (IOW: backporting to earlier, still supported series) at all.
And I'm mostly fine with it. But I think it's wrong when it comes to recent mainline regressions that bother users.
Especially when they cause severe damage like disk corruption (as seen by multiple reporters), as it this case:
https://lore.kernel.org/all/20241003160454.3017229-1-Basavaraj.Natikar@amd.com/
Backstory: https://bugzilla.kernel.org/show_bug.cgi?id=219331 & https://lore.kernel.org/all/90f6ee64-df5e-43b2-ad04-fa3a35efc1d5@leemhuis.info/
@kernellogger Do you have anything watching rates of reports on different CPU types? It was surprising that turned out as AMD until the bisect pointed the finger.
Nope. 
Hopefully sooner or later someone will first revive/rewrite kerneloops[1] and afterwards makes things like that possible, too.