@warthog9 @argv_minus_one

I’d argue this not having a broader security push before the public release happened, is a pretty serious failure on someone’s part.

And who is that “someone”? We fix bugs like this in the kernel on a daily basis. If people have not learned to constantly upgrade to stay ahead of this, then why even assign these 10 CVEs a day in the first place? :)

@jeroen Don't trust the Mhz numbers, when the system is overloaded like that, it's hard to report what is actually happening. The load average is over 2000 so it's amazing anything is being reported properly.

Once again, my professional recommendation in response to the latest Linux kernel vulnerability in the news is that you should gather up all your electronic devices, cast them into the sea, and retreat to the woods.

Each night, gather your children and tell them tales of the Before Times when the hubris of humanity grew so large that we made idols of sand and spoke to them as equals. Remind them that the sand, of course, did not speak or think, but we imagined it could, and let it guide us to folly.

Should a stranger ever come to your village with a glowing rectangle, encourage the youth to beat them with sticks.

#infosec

My build system right now, as it's one of "those" mornings....

I was explaining how we built #bluefin with buildstream and bootc to a coworker and he goes.

"So you made Gentoo but cloud native."

And now I am never going to shut about it lol.

@qualcuno I don't remember, sorry. We got it as a gift many years ago.

@nklsdev As stated above, all of them!

@darakian All of them!

@qualcuno Yup!

As people keep guessing what/who `gkh_clanker_t1000` is: https://lore.kernel.org/r/20260424054143.087847e1617a84df8b501313@linux-foundation.org

here it is after I cleaned up some of the horrid cable mess that had grown up around it.

We now require proof of work before you can submit a #curl security report.

Like mowing @bagder 's lawn or washing his car.😌

@qwertviop @AdrianVovk Thanks, found it, but no, nothing, all seems sane on the system. Oh well, KDE it is until I wipe this box...

@lesto Yes to the first, and for the second "you can always change the code to adapt over time". Make it work now, don't worry too much about the future as you don't know what it will hold.

@qwertviop @AdrianVovk there is no `paccheck` as part of `pacman-contrib` :(

@tmpjg Yes, I am, but that's not the one I "broke", and I have another box from him sitting right here that I need to get up and running as the old one is showing its age...

@AdrianVovk Thanks for the hints. I deleted all of that and still no luck. But in digging in the lots, looks like it is gnome-shell that is failing to run, it crashes, so something is very odd.

I had pacman check all packages, and nothing seems out of the ordinary, so who knows...

I'll just live with kde for a bit, it's a nice change for a bit.

@Aissen @gregkh @ljs @vbabka Ah had not even seen that. It's not bitter sweet, removing code is a Good Thing, and now there's finally a reason to do it that carries some weight. Before this ordeal, it was always punted with "ah well the maintenance burden isn't THAT big". Kill it with fire, git history is forever and if someone steps up to properly maintain a piece of code, it can be brought back.

We're not running a museum.

@brauner @axboe You most certianly deserve a crate of whatever you want!

After 25+ years of kernel development, I was finally forced to touch `mm/` and it was due to a nommu "issue":
https://lore.kernel.org/lkml/2026042334-acutely-unadorned-e05c@gregkh/

As @axboe said the other day, we aren't expecting a box of chocolates:

https://lore.kernel.org/r/2f2c91cb-f20e-44eb-8ba3-2d5b3d649642@kernel.dk

but these past weeks have made me feel like someone owes a few of us kernel developers a bunch of whisky at the very least...

@musicmatze Been there, done that, gave up as I just want to get real work (i.e. kernel stuff) done faster.