@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.

@chergert I blew those away, still nothing :(

After totally messing up my gdm configuration by foolishly using `gdm-settings` (I didn't want the machine to suspend at the login screen for obvious reasons that doesn't play well with logging into it from other boxes), causing it to not properly even show a login screen, I've reverted back to running plasma and realizing it's been a long time since I last ran KDE and how nice it's gotten since then.

So, until I figure out how to wipe all gdm settings from the system (hint, I tried the "reset" option on gdm-settings and to blow away all dconf files that i could find on the disk, but odds are I missed something), I guess I'm now a KDE user until I move to a new system...

The #Linux 6.19.y series is now end of life:

""This is the LAST 6.19.y kernel to be released, this branch is now end-of-life. Please move to the 7.0.y kernel branch at this point in time.""

https://lore.kernel.org/all/2026042220-coastline-flirt-ad3c@gregkh/

http://git.kernel.org/pub/scm/docs/kernel/website.git/commit/?id=0287316cba72ac42454cb5befd7528bde4886d28

#LinuxKernel #kernel

"During one of my presentations at Open Source Summit Japan🇯🇵 the past year, I talked about a bug I found while addressing -Wflex-array-member-not-at-end issues in the Linux kernel. [...]

[...] not-at-end FAMs are a compiler extension that may cause undefined behavior, and compilers don't handle the sizes of objects containing them consistently. For this reason, they are now deprecated..[...]"🐧

https://embeddedor.com/blog/2026/04/18/wflex-array-member-not-at-end-and-a-misalignment-bug-in-the-linux-kernel/ 🐧

#Linux

We get randomest crap.

@jlhertel That doesn't seem to actually provide the "what function/symbol is modified" logic, nor would I expect it to, unless I am missing something obvious?

@chinmay @wilfredh So, "if a new option was added to this tool" kind of doesn't solve the issue today, or even tomorrow, if no one is adding such an option. Are you suggesting I do that? That's fine if you are, maybe that's the best end result, don't know, just want to make sure I'm not missing something already out there today.

@neverpanic @mxk I thought mergiraf is for merges, not a "simple" diff, that has no merge conflicts, am I missing something?

And yes, "taking code from elsewhere" is great, and I can do that, but wanted to make sure there wasn't something out there that already handled all of this before going down that yak-shaving path...

@mei Not all that much, "best effort" is fine.

@chinmay @wilfredh difftastic is great, but a visual tool, not something that can be hooked up into a script to generate the list of modified symbols as far as I can tell. But again, I might be missing an option there, am I?

Dear semi-lazyweb,

Given a git diff of a C/Rust codebase, how to best determine which functions/defines have been modified between the two versions? Yes, the diff itself sometimes gives hints as to what has changed, but it's not always correct. Think about when it modifies the start of a function, but the diffstat "name" shows the previous function, a correct marking, but not what is needed.

Is the correct answer really going to be "compile the two versions and compare the AST" or something like that? No "diff library" somewhere that "knows" how to parse C (and Rust) that can do this in a faster way? Surely I'm missing something obvious here...

There is virtually **no** AI slop security reports anymore submitted about #curl. They don't seem to happen any longer.

Almost everyone still uses AI though.

1. GenAI is probably going to impact us but how? Nobody knows.
2. The worst thing about GenAI isn't the technology, it's the shitty people: https://karlbode.com/the-problem-with-ai-is-shitty-human-beings [<must-read]
3. We can’t have a grown-up conversation on the subject because the trillion-dollar bet’s fear+greed pressure crowds out truth.
4. When the bubble pops, the shitty people will melt away. Then we can maybe figure it out.
5. We so *SO* need that bubble to pop. Next week would be ideal.

#GenAI

you ever write code so inefficient they have to update the whole power grid