Posts
440
Following
101
Followers
4720
gregkh

Greg K-H

Reply to @qualcuno@livellosegreto.it
@qualcuno Yup!
1
0
1
gregkh

Greg K-H

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.
4
18
64
gregkh
repeated
icing@chaos.social

Stefan Eissing

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

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

2
7
1
gregkh

Greg K-H

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

Greg K-H

Reply to @lesto@hachyderm.io
@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.
0
0
0
gregkh

Greg K-H

Reply to @qwertviop@chaos.social
@qwertviop @AdrianVovk there is no `paccheck` as part of `pacman-contrib` :(
1
0
0
gregkh

Greg K-H

Reply to @tmpjg@rebel.ar
@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...
0
0
1
gregkh

Greg K-H

Reply to @AdrianVovk@fosstodon.org
@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.
1
0
1
gregkh
repeated
axboe@fosstodon.org

Jens Axboe

Reply to @Aissen@social.treehouse.systems

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

1
3
2
gregkh

Greg K-H

Reply to @brauner@mastodon.social
@brauner @axboe You most certianly deserve a crate of whatever you want!
0
0
3
gregkh

Greg K-H

Edited 28 days ago
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...
3
9
31
gregkh

Greg K-H

Reply to @musicmatze@social.linux.pizza
@musicmatze Been there, done that, gave up as I just want to get real work (i.e. kernel stuff) done faster.
1
0
8
gregkh

Greg K-H

Reply to
@chergert I blew those away, still nothing :(
1
0
1
gregkh

Greg K-H

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...
7
5
37
gregkh
repeated
kernellogger@hachyderm.io

Thorsten Leemhuis (acct. 1/4)

The 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

2
2
1
gregkh
repeated
gustavoars@fosstodon.org

Gustavo A. R. Silva tux

"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/ 🐧

0
2
0
gregkh
repeated
monsieuricon

K. Ryabitsev-Prime 🍁

We get randomest crap.
1
10
34
gregkh

Greg K-H

Reply to @jlhertel@fosstodon.org
@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?
1
0
0
gregkh

Greg K-H

Reply to @chinmay@social.treehouse.systems
@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.
1
0
2
gregkh

Greg K-H

Reply to @neverpanic@chaos.social
@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...
1
0
2
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: