Linus Torvalds released Linux 7.4-rc2 on Sunday 8 November 2026 (US Eastern time) and opened with: “Ok, a big -rc2 to go with the largest ever -rc1.”
What the announcement says
Torvalds says the diffstat “looks fairly benign”. It is dominated by automated coccinelle updates he received for the merge window but held for rc2. Those scripted changes are “largely just one- and two-liners”, spread across thousands of files, so they add noise rather than risk. With that noise masked out, he describes the rest as roughly a third drivers (mostly GPU, networking and sound), a third networking and BPF, and a third everything else (mostly filesystems, memory management and arch updates).
Then the AI part, quoted in full:
And yes, much of this was driven by various AI fixes. I think I’ll stop repeating that, and we can just take it for granted. But this time around Alexei claims that on the bpf side at least the fixes are now coming in faster than the new reports, and that sounds lovely if true.
He adds that “most other areas haven’t reached that point yet”, that it is “at least a sign that we may be starting to see the tide starting to turn”, and: “Don’t hold your breath, but maybe cross your fingers.”
How to read it
Three things are in the text, and one is not:
- In the text: AI-driven fixes are now routine enough that Torvalds will stop mentioning them each week.
- In the text: “Alexei”, which in BPF context means Alexei Starovoitov, a BPF maintainer listed in the kernel’s MAINTAINERS file, claims BPF fixes are arriving faster than new reports. Torvalds relays it with “if true”.
- In the text: other subsystems are not there yet.
- Not in the text: a kernel-wide count, a statement that the AI report flood has peaked, or any number for AI-assisted commits. Coverage that adds those is citing other sources.
This is the kernel side of a pattern we have tracked: Torvalds himself publishing a Claude Code branch, and Robert Haas saying LLM-found bugs delayed PostgreSQL 19.
Why this matters
For maintainers swamped by AI-generated reports, this is the first time the kernel’s release notes name a subsystem where the fix rate is claimed to beat the report rate, and it is hedged and limited to BPF. If you ship eBPF-based networking, observability or security tools, networking and BPF make up about a third of rc2 by Torvalds’ count, so it is worth testing against before 7.4 final. For your own project, the transferable part is Torvalds’ framing: treat AI-found bugs as normal intake, and measure fixes against new reports per area rather than counting reports alone.

The Campfire
CommentsThanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.
Add a comment