ebel auroraThe wrong people have imposter syndrome
relapsing former social media user
Linux kernel developer @ SUSE Labs Prague
Slava Ukraini!
Glory to the Heroes!
fuck putin, trump, musk and other cowardly pricks
also fuck netanyahu
also fuck communism
Vlastimil Babka π¨πΏπͺπΊπΊπ¦
@vbabka
- 277 Followers
- 269 Following
- 3.2K Posts
Tomas Vondra@AndresFreundTec @thesamesam @mgorny I think the bigger issue is the strange definition of what "LTS" means, and what people assume it to mean. Because from the descriptions I found, LTS means "actively maintained and provided with security updates" but it seems it means "some security updates, maybe". Which is not great, I guess?
FWIW I understand the number of fixed issues is likely overwhelming. But then maybe not having LTS kernels would be better ...
Oleksandr Natalenko, MSE 
Surprised pikachu face after learning that "stable" kernel is just an LLM-shuffled
master branch with random commits dropped.
AndresFreundTec@thesamesam @mgorny The "you must update to the latest release
to get all fixes needed to keep a system secure of all currently-known
issues" bit really makes my head explode.
How does GKH expect folks upgrade all their prod systems every ~6 days (the rough average release pace of -stable kernels), with sometimes as much as four releases in a week.
That's unrealistic CYA language, and GKH has to know that.
@gregkh @joshbressers Of course companies hate it.
Plenty for bad reasons.
But also for reasonable ones: Who can afford to reboot all machines every few days? 6.18 averaged a stable release every ~5.6 days, 6.12 averaged one every ~6.15 days.
If you continually ask for unrealistic things ("All users of the xyz kernel series must upgrade." > once a week), folks *have* to stop listening after a while.
What do you expect folks to actually do with prod systems?
Vadim Rutkovsky
Angie
OndΕej CaletkaAndroid now stops you sharing your location in photos
(β¦and there's apparently no way of saying βI know what I'm doing, please keep my photos intactβ π€¬)
https://shkspr.mobi/blog/2026/04/android-now-stops-you-sharing-your-location-in-photos/
Android now stops you sharing your location in photos
My wife and I run OpenBenches. It's a niche little site which lets people share photos of memorial benches and their locations. Most modern phones embed a geolocation within the photo's metadata, so we use that information to put the photos on a map. Google's Android has now broken that. On the web, we used to use: β§ HTML<input type="file" accept="image/jpeg"> That opened the phone's photo pβ¦
sam@mgorny Compare Solar Designer's attempt to find a compromise at https://www.openwall.com/lists/oss-security/2026/05/01/2 with the response at https://www.openwall.com/lists/oss-security/2026/05/01/3
I don't think I can keep commenting on this, because it's driving me mad. I've already tried to be very restrained in what I say.
Jesus MichaΕ "Le Sigh" π (he)Greg Kroah-Hartman: "If you look there are thousands of unfixed CVEs in the older LTS kernels right now, and if distros or users that rely on those older branches wish to see those resolved, they need to provide working backports to us to apply, as our first attempt did not work (which is why they are unfixed in those branches.)"
Really asking for a "Pray tell us", given that nobody actually bothered disclosing the problem to downstreams and that the commit message was hiding it.
Either way, apparently the great LLM-backed patch backporting process that #NVidia is so proud of doesn't really work. Upstream doesn't really care about #LTS branches, and they should be considered insecure by default.
https://lore.kernel.org/stable/2026050114-supernova-angler-2de1@gregkh/