Posts
485
Following
100
Followers
5032
repeated

"Executives working on AI at Microsoft and OpenAI admitted what its critics have been saying all along: Large language models are predatory pieces of technology that have been built on what a Microsoft executive called “an astonishing theft of unprecedented proportions,” and the “largest theft of labor in human history.” An internal Microsoft document said generative AI products have created a “doom loop” that is killing “the entire web.”"

(Article title: ‘Doom Loop’: OpenAI and Microsoft Admits LLMs Are Destroying the Web and Built on Theft)

https://www.404media.co/doom-loop-openai-and-microsoft-admits-llms-are-destroying-the-web-and-built-on-theft/

2
6
1
repeated
Edited 3 days ago

"for months on end now, most of our teams have just been triaging bugs and coordinating releases. It has truly taken all the fun out of the job"

https://blog.nlnetlabs.nl/maintaining-the-love-for-coding-in-the-time-of-ai/

9
13
1
repeated

Thorsten Leemhuis (acct. 1/4)

Looks like the legacy C implementation of the IPC driver will soon be removed from in favor of its version:

https://lore.kernel.org/all/rm-c-binder@google.com/

""Long live the new Rust Binder king!""

4
8
0
Edited 7 days ago

This might be a “record” for stable kernel -rc releases. Not really a record I want to ever beat…

     version  queued
	5.10:	 798
	5.15:	 935
	6.1:	1191
	6.6:	1424
	6.12:	1376
	6.18:	1518
	7.2:	1815
	total:	9057
3
3
22
repeated

The September 11 CRA reporting milestone is here.

Our new community guide explains manufacturers’ reporting obligations and how open source maintainers and stewards can prepare for collaboration when vulnerabilities affect downstream products.

https://openssf.org/blog/2026/09/11/a-community-guide-to-the-eu-cra-september-11-deadline-for-manufacturers/

0
1
0
repeated

Open Call for Nominations: European Open Source Awards 2027

Please consider taking a minute and tell us who we should recognize and honor this time around! We need to know about the heroes to be able to celebrate them.

https://awards.europeanopensource.academy/nomination-process

1
5
0
I can't resist keyboards in "odd" formats...
2
3
38
For anyone "worried" that the CRA was going to cause some reporting requirements as of September 11, 2027, the EU has answered that question and updated their FAQ with in section 5.5 that says we only have to start reporting in December 2027:
https://digital-strategy.ec.europa.eu/en/library/cyber-resilience-act-implementation-frequently-asked-questions
So while many of us were ready to start the reporting process, it is good that we have a bit more time for the tools and infrastructure to get solid before we have to start using it.
2
7
21
repeated

Thorsten Leemhuis (acct. 1/4)

7.1 is now unsupported upstream – @gregkh just announced that while releasing 7.1.13 and a bunch of other new stable and longterm releases:

""Note, the 7.1.y kernel series is now end-of-life. Please move to the 7.2.y kernel series at this point in time.""

https://lore.kernel.org/all/2026090223-botanical-purging-2933@gregkh/

0
2
1
repeated

v262~rc1 is out! If you don't help testing it out, YOUR favourite third party service will be next on the takeover list

https://github.com/systemd/systemd/releases#release-v262-rc1

1
5
0
repeated

Things don’t seem to be slowing down in kernel development world, even for old subsystems that should be “stable”. Here’s my “todo” mbox filtered for linux-usb stuff, that has come in in the past few weeks:

---Mutt: =todo [Msgs:1732/4807 Inc:2 78M]---

This is going to be a rough -rc cycle…

3
5
32
repeated

The EU Cyber Resilience Act is reshaping responsibility across the software supply chain.

In the latest What’s in the SOSS?, Madalin Neag breaks down what the CRA means for open source, software stewards, maintainers, and organizations preparing for compliance.

https://openssf.org/podcast/2026/09/01/whats-in-the-soss-podcast-71-s3e23-navigating-the-new-era-the-eu-cyber-resilience-act-explained-with-madalin-neag/

0
1
0
repeated

Thorsten Leemhuis (acct. 1/4)

Edited 20 days ago

The video recording of @gregkh's recent keynote "Linux in the Land of LLMs" is now available on YouTube: https://www.youtube.com/watch?v=_MwMLPmMccs&pp=0gcJCRMMAYcqIYzv

Slides: https://hosted-files.sched.co/osskorea2026/a7/4%20-%20Greg%20-%20oss_korea%20v2.pptx.pdf

Here are a few screenshots from the latter:

0
3
1
Some talks just write themselves, @KernelRecipes is going to be fun this year!

(not that it's not fun every year, but you get the idea...)
9
42
90
repeated

If you're interested in the design of agentic workflows, remember this formula:

R = 1 - (1 - P)(1 - C)

0
3
0
repeated

David Chisnall (*Now with 50% more sarcasm!*)

Edited 1 month ago

This article starts with a story from someone who tried Claude Code and found it amazing, but then switches to the same person a few months later seeing what a disaster it’s been. This quote is key:

The problem is that code produced by an AI agent looks reasonable, but can contain ‘hard-to-spot bugs’ that end up causing major problems

LLMs, by their nature, generate statistically plausible output. That is often a set that overlaps with correct output. But the things that are not correct look exactly the same as the ones they are.

Learning to review code is hard. You look for the bugs that you expect to be possible implementing it by using your theory of mind for the person writing the code and the kinds of things that they might overlook (not necessarily a specific person, but the kinds of things people miss) and also common bug classes.

And the big help is that the person writing the code is not thinking adversarially. They are not trying to sneak bugs in. Normally. Unless they’re a supply-chain attacker, and we’ve a depressing amount of evidence that code review doesn’t catch supply-chain attacks.

An LLM is not trying to do anything. It has no intent. But it is a machine that is trained on code that made it past code review. The kind of bugs that it will generate are ones that look like code that appeared in production. This is exactly what an attacker would do: try to write code that looks correct but is subtly wrong.

I’m only being slightly flippant when I say LLMs are a mechanism for bringing supply chain attacks in house.

12
18
1
In which I explain how I will treat LLM generated or assisted patches for the Linux kernel drivers/staging/ subsystem going forward:
https://lore.kernel.org/all/2026080354-skater-urgent-31b2@gregkh/T/#u

(hint, not allowed, except for security bugs that you can prove actually fix something by testing the issue on the actual hardware the driver controls.)
8
104
161
repeated

Meet the 2026 Kernel Recipes mascot.

Curious, optimistic, and very much in tune with the world around it.

This year, our little penguin is thinking beyond code. From sustainability to responsible tech, it reflects values that have always been close to the open source community.

With the devastating wildfires affecting France this summer, it also reminds us that technology doesn't exist in a vacuum. The challenges we face are shared—and so is the responsibility to build a better future.

1
6
1
Another one of those mornings....
7
5
40
Show older