Linus Torvalds said AI-assisted coding tools have made unusually large Linux kernel updates the new normal for the project [1, 2].
This shift indicates that generative AI is now producing a volume of code that significantly alters the traditional pace and scale of open-source development. As these tools generate larger patches, the project must balance rapid growth with the stability of the world's most widely used kernel.
In a weekly "state of the kernel" message posted on Monday, Torvalds referred to the previous week's release candidate [1, 2]. "This rc is huge," Torvalds said [1]. He said that the increased size of these updates is a direct result of AI tools generating substantial patches [1, 2].
Despite the increased volume of code, Torvalds said the upcoming Linux kernel version 7.2 will not be delayed [1].
Torvalds has faced criticism from developers who oppose the use of AI in the kernel. In response to those critics, he said, "Fork it. Or just walk away" [2]. He said that the project is not anti-AI, emphasizing that the strength of open-source software is that it is open, meaning anyone can contribute [3].
This openness has led to a divide within the community between developers using AI and those who are anti-AI absolutists [3]. Torvalds has previously offered a more skeptical view of the technology's early promises. He said that in 2024, AI was 90% marketing and 10% factual reality [4].
While the practical impact of AI was viewed as limited a few years ago, the current size of release candidates suggests the technology has integrated more deeply into the development workflow [1, 4].
“"This rc is huge."”
The integration of AI into the Linux kernel development process represents a transition from experimental use to systemic impact. While the volume of contributions is increasing, the primary challenge for maintainers is now the verification of AI-generated code at scale. Torvalds' refusal to delay version 7.2 suggests that the project's infrastructure can currently absorb this increased velocity without compromising the release schedule.
