At the recently concluded Maintainers Summit, Linus Torvalds openly admitted he had used a large language model to draft a patch series tackling a long-standing kernel bottleneck — and has now posted the first 10 patches to the Linux Kernel Mailing List for review. This is the first time Linus has formally submitted LLM-assisted code to LKML.
What the patches actually fix
The series targets the folio lookup path. Folios — the kernel data structure that groups multiple physical pages — are used almost everywhere a file is read, mapped, or handed to the I/O subsystem; contention on folio reference counts and locks has long been one of the hottest optimization targets.
The approach is direct: detect "hot" folios (those that are repeatedly accessed) and set a flag that defers their release until after a grace period. RCU (Read-Copy-Update) is the kernel's classic synchronization primitive for read-mostly workloads, built on the idea that readers are nearly lock-free while writers delay reclamation. Folio lookups themselves under RCU protection are nothing new — but this series goes one step further: the actual folio data accesses themselves happen under RCU, eliminating the need to grab a reference count on the fast path.
Performance and the known bug
According to Torvalds, on a read-heavy benchmark the changes deliver an order-of-magnitude speedup — not the usual few-percent-to-double gain you see in mature subsystems, but a 10x-class jump. That kind of leap has been rare inside the kernel for a long time.
Review on LKML, however, has not been gentle. The patches were barely out the door before the community identified a race condition that will need further fixing. Which is, in a sense, exactly what Linus wanted: at the Summit he said the real test of LLM-written code is not how the model writes it, but whether the community's review process is rigorous enough to send it back for work.
Why it matters
The signal value here is bigger than the patches themselves. Over the past two years, Linus has been openly skeptical of AI-generated code, and communities like NetBSD have gone so far as to label such submissions as contamination and refuse to accept them. This time Linus stepped up himself, handed a kernel subsystem he understands best to an LLM to draft, and put the result through the full LKML review chain.
In other words, "can LLM code land in mainline?" has been turned from a philosophical question into an engineering question: does it pass review, does it bisect, does it survive long-term testing. The criterion is not authorship — it is quality.
The path from cold start to LKML now exists. The next checkpoint to watch is whether any of these patches get pulled into an mm or folio-related maintainer's tree during the -rc1 merge window.