Linus Torvalds uses Claude Code for kernel patches; reviewer flags a race
10/16/2026 — 10/16, 19:19·2 sources (all)·2 reports (all)
Key takeaways
- Linus Torvalds used Claude Code to write a set of Linux page-cache fixes that lifted read throughput 23x on a synthetic Ryzen Threadripper b…
- follow-up work has since been handed to others.
Background & analysis
In October 2026, Linus Torvalds, the creator of Linux and its long-time lead maintainer, turned to Anthropic's Claude Code to tackle a kernel performance problem that had dogged developers for more than two years. He submitted a series of 10 patches that remove folio reference counting operations from the common buffered read path. In synthetic benchmarks run on a Ryzen Threadripper, the series lifted read throughput by 23x, though Torvalds cautioned that the gain would be much smaller under real workloads. He had previously spent 18 months running a flawed fix of his own in an attempt to resolve a reference counting bottleneck in the page cache, and proposals from other developers had also run into problems.
Before the patches were merged, kernel reviewer Kiryl Shutsemau flagged a race condition in filemap_read_rcu_batch(): if a folio is replaced and the file size (i_size) is then extended, the read path could return data that has not yet been written to the file back to a user program. The reviewer also raised questions about the patch series' memory reclaim mechanism. Torvalds has handed further development to Shutsemau, who had also studied this bottleneck before.
AI-generated from 1 reports · updated 8 hours ago
Latest turnLinus Torvalds used Claude Code to write a 10-patch series fixing a page-cache bottleneck in the Linux kernel, boosting read throughput 23x on a synthetic Ryzen Threadripper benchmark — though he cautioned the gain would be much smaller on real workloads. Before the patches were merged, kernel reviewer Kiryl Shutsemau spotted a race in filemap_read_rcu_batch() that could return unwritten file data to user programs, and follow-up work has been handed to him.
Related AI tools
- Heat index
- 195
- All sources
- 2
- All reports
- 2
- First seen
- 8 hours ago
Reports on this story headlines open the original
Linus Torvalds used Claude Code to write a 10-patch series fixing a page-cache bottleneck in the Linux kernel, boosting read throughput 23x on a synthetic Ryzen Threadripper benchmark — though he cautioned the gain would be much smaller on real workloads. Before the patches were merged, kernel reviewer Kiryl Shutsemau spotted a race in filemap_read_rcu_batch() that could return unwritten file data to user programs, and follow-up work has been handed to him.
InfoQ 中文AI score 74According to Tom's Hardware, Linux creator Linus Torvalds has submitted his first LLM-assisted patch to the Linux kernel, after publicly backing AI tooling in kernel development. The report cites a synthetic test showing a 23x performance leap, though that figure comes from a synthetic benchmark rather than real-world workloads.
Tom's HardwareAI score 67
Other stories people are talking about
- Heat index 36Linus Torvalds Pushes Linux Kernel Patch Written With Claude Code1 sources
- Heat index 50Tutorial: building an auto-shop admin system with Claude Code1 sources
- Heat index 63Developer compares commands across Claude Code, Codex, Gemini CLI1 sources
- Heat index 63Developer compares 18 CLI commands between Claude Code and Codex CLI1 sources
- Heat index 84Claude Code 2.1.299-2.1.301 change hooks behavior in seven ways1 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion
