Posts
327
Following
92
Followers
3471
gregkh
repeated
till@ubuntu.social

Till Kamppeter

Edited 13 days ago

Urgent help for OpenPrinting needed!

As many here know, I am co-founder and lead of OpenPrinting since 2001, known as the print guru for Linux and free software by many. I also got one of the 8 fellows of the Linux Foundation for this.

Up to now I was working at Canonical, hired back in 2006 just to run OpenPrinting and also to maintain printing-related Ubuntu packages.

... 🧵

Please boost.

26
62
0
gregkh

Greg K-H

Reply to @trini@floss.social
@trini Contact the CNA that created it and get them to reject it, if they don't complain to cve.org.
1
0
1
gregkh

Greg K-H

Reply to @larsmb@mastodon.online
@larsmb Ah, you seem to have run into a "slopper" https://www.todayintabs.com/p/we-need-to-talk-about-sloppers-b732?_bhlid=cf776e870f09f7dd3876c6b20616bf9a25b260fd
2
0
2
gregkh

Greg K-H

Reply to @stsquad@mastodon.org.uk
@stsquad @hrw Fixing the lack of almost all riscv soc drivers to be upstream so that I can boot a kernel.org release on one of them (i.e. a normal developer can test their changes) would be a good start. Which is one of the things that article says...
1
0
5
gregkh

Greg K-H

Looks like the risc-v community is learning from history! Hopefully this results in more upstream development efforts: https://riscv.org/blog/2025/07/risc-v-upstreaming/
2
29
34
gregkh

Greg K-H

Reply to @jarkko
@jarkko This all happened _WAY_ before ebpf was even a thing...
1
0
0
gregkh

Greg K-H

Reply to @vbabka@mastodon.social
@vbabka AUTOSEL is there because maintainers and developers do not, or forget to, properly tag "Cc: stable@kernel.org" for their bugfixes.

If they all did that, we would never need to use AUTOSEL at all.

But you know that, stop trying to feed the trolls. It's a beautiful day outside, enjoy it! :)
0
0
0
gregkh

Greg K-H

Reply to @jarkko
@jarkko Groups (i.e. big companies) have tried to come up with a standard way for all kernel log messages, as that is what they were used to for their "other" operating systems. They wanted a big book, they could reference, to look up what each message meant and what to do about it if it showed up.

After many "discussions" with the community, I think in the end they got something they could use on the back-end to tokenize the kernel messages from the source, and somehow create unique identifiers they can use in other tools, but I don't remember the specifics. Odds are it's buried in the kbuild system somewhere....
1
0
1
gregkh

Greg K-H

Saving this here to use later. As seen in the comments on yet-another-ai story on Lobsters:

"How could you claim to have a neutral, informed opinion on LLMs without signing up for a bunch of subscriptions and constantly talking to the liar machine to see if it told a truth today?"
2
20
40
gregkh
repeated
icing@chaos.social

Stefan Eissing

One of my fav quotes from this @gregkh interview:

"Open source ends up having better depth of knowledge than closed source has."

(Because for careers in companies you get shifted around while many people in OSS stay in the same field/code for decades.)

https://www.youtube.com/watch?v=-1-OjxPJZcs

0
3
2
gregkh
repeated
brauner@mastodon.social

Christian Brauner 🦊🐺

7
9
4
gregkh
repeated
linkersec@infosec.exchange

Linux Kernel Security

Linux Kernel Hardening: Ten Years Deep

Talk by @kees about the relevance of various Linux kernel vulnerability classes and the mitigations that address them.

Video: https://www.youtube.com/watch?v=c_NxzSRG50g
Slides: https://static.sched.com/hosted_files/lssna2025/9f/KSPP%20Ten%20Years%20Deep.pdf

0
7
0
gregkh
repeated
monsieuricon

K. Ryabitsev 🍁

All the slides at this meeting talk about how much time and effort "AI" would help us save, and all I want to do is point out how much time and effort I've sunk so far into keeping AI crawlers from DDoS'ing our infra.
1
39
75
gregkh
repeated
winload_exe@wetdry.world

pivotman319 🦊 aromantic flagace

Reply to @gregkh

@gregkh linters literally do their job better than a speculation machine

1
1
1
gregkh

Greg K-H

Reply to @ptesarik@infosec.exchange
@ptesarik That's what `drivers/staging/` is for, we just took 10+ patches for that subsystem from new submitters yesterday. That's much easier to accomplish than trying to parse the output of an "AI tool" :)
1
0
5
gregkh

Greg K-H

Reply to @liw@toot.liw.fi
@liw We assign 13 CVEs for Linux every single day. "Fame and fortune" is not something that happens for any of those reports, as a CVE is trivial to get if you actually want to just fix a kernel bug for real.
2
0
7
gregkh

Greg K-H

Days since an "AI found security bug" turned out to be totally false due to the inability of the tool to actually parse C code: 0

I'm seeing multiple of these type of "reports" per week now for Linux. Why do people think that an LLM can somehow do better than a compiler and also not even test their proposed changes to verify they even do anything?

{sigh}
21
101
160
gregkh

Greg K-H

Reply to @codonell@fosstodon.org
@codonell @brauner Yes, just add them at the end.

And we don't use the "(cherry picked from..." text in the kernel for stable backports, we do a much larger "commit XXXXXX upstream" at the top of the changelog text to make it easier for tools to catch.
0
0
0
gregkh

Greg K-H

Reply to @brauner@mastodon.social
@brauner @codonell That is correct, in the kernel we do NOT clear any of them out, only add new ones as that would "erase" the work that the original developers/reviewers did on the original change, which isn't a kind thing to do in my opinion.
1
0
1
gregkh

Greg K-H

Reply to @nitrokey@nitrokey.com
@nitrokey Thanks, will do!
0
0
1
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: