On Wed, 2025-09-17 at 23:50 +0200, Uwe Kleine-König wrote: > My interpretation is that 2640e819474f (i.e. a commit not present in > the > Debian kernels yet) is needed to make this problem considerably more > likely to occur. So I'd expect that yes 6.16 has a problem, but it > doesn't trigger often.
Well I can't judge that. I've been running since you guys uploaded 6.16 to sid wiht that... and at least haven't noticed any breakage. But if someone's writing his thesis and picks that 1 in 10000 chance where it even hits there, he might not be pleased. ;-) > Applying a commit fast to the Debian kernel also has the downside to > skip over a maturation process. While I would consider Rafael's > judgement a strong hint and the patch simple enough to consider the > change safe enough, there is a good reason the Greg Kroah-Hartman > sends > out the patches he queued for the upcoming stable release to the > mailing > list. There is an armada of people and bots that review and do build > and > runtime tests that is very valuable. Sure :-) Good enough for me. As said I merely meant this as a heads up so that the kernel team can judge whether it's worth the risks to cherry pick or not. Thanks, Chris.
