Torvalds Joked that AI Made Linux 7.3-rc2 this Big, and Nobody Checked
Linus Torvalds signed off an unusually heavy Linux 7.3-rc2 by suggesting everyone blame AI, with a wink. A month earlier he said the same thing without one. The kernel now asks contributors to tag machine-assisted patches, so the question is answerable. Nobody has published the number.
What is Actually Inside Linux 7.3-rc2
An rc2 is normally a quiet week. The merge window has shut, everyone breathes out, and bug reports have not started landing yet. This one behaved like a merge window that refused to end. Several filesystems sent fixes. The graphics tree sent a sizeable pull of scattered ones. Networking, bpf, and a run of driver trees all filed too.
Torvalds pointed at a late EDAC pull that missed the merge window, then dismissed it himself as a small thing. A week earlier he had blamed the size of rc1 on an AMD GPU register dump, and on himself. Neither explanation stretches to cover rc2.
The Most Useful Line in the Whole Post
The most useful line in the whole post has travelled least. Tooling accounts for roughly 20% of the entire patch, mostly sched_ext and selftests. Drivers always dominate a kernel release. Outside them, tooling is now the biggest source of change, ahead of filesystems, core kernel, and networking. That is test infrastructure growing, not features.
Torvalds Answered This Question Seriously a Month Ago
Announcing 7.2-rc7, Torvalds said he was not thrilled about the size of it. Then he gave a straight causal account. This is the new normal, he wrote, with a lot of fixes, many of them the product of review by various AI tools. No emoticon that time.
The Register reported the rc2 line on Monday. Its APAC editor, Simon Sharwood, has tracked these Sunday posts through the whole cycle. The August statement is the one that matters more, because it draws a distinction the September joke collapses.
Machines reviewing code and flagging bugs is not the same thing as machines writing code. The first produces a flood of small, scattered fixes and a lot of new tests. That is what rc2 looks like. The second produces a failure mode TNW has covered repeatedly, where generated code fails security tests at rates its authors did not expect.
The kernel already built the instrument to settle this.