https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #4 from Theodore Tso (tytso@xxxxxxx) --- Thanks for pointing out that bug. I'll note that the poster who authoritatively claimed that 4.19 is safe, and the bug obviously was introduced in 4.19.1 didn't bother to do a "git log --stat v4.19 v4.19.1". This would show that the changes were all in the Sparc architecture support, networking drivers, the networking stack, and a one-line change in the crypto subsystem.... This is why I always tell users to report symptoms, not diagnosis. And for sure, not to bias their observations by their their certainty that they have diagnosed the problem. (If they think they have diagnosed the problem, send me a patch, preferably with a reliable repro so we can add a regression test. :-) -- You are receiving this mail because: You are watching the assignee of the bug.
