Linux Kernel 7.1-rc3 Released: Larger Patches Becoming the 'New Normal'
Breaking News: 7.1-rc3 Released
Linus Torvalds released the third release candidate for Linux kernel 7.1 on Sunday, confirming that the unusually large patch sizes first observed in version 7.0 are not an anomaly but a permanent shift in kernel development. The release candidate weighs in at a size comparable to its predecessor, indicating that kernel developers are now submitting more code per cycle than ever before.
In a mailing list announcement, Torvalds stated: “This answers the ‘is 7.1 continuing the larger size pattern that we saw with 7.0?’ question—and the answer is yes: that wasn’t a fluke brought on by a dot-zero release. It simply seems to be the new normal.” The comment signals a structural change in the Linux kernel’s development pace and resource demands.
Background
The Linux kernel has traditionally seen spikes in code volume during .0 releases, followed by smaller incremental updates. However, starting with 7.0 in early 2025, the development community observed a sustained increase in patch submission rates. 7.1-rc3 marks the second consecutive kernel cycle where that trend holds, suggesting that factors such as expanded hardware support, growing driver ecosystems, and continuous security hardening are driving the higher volume.
Kernel maintainers had initially attributed the 7.0 size to the typical “merge window bloat” associated with a major version. Torvalds’ latest remarks dispel that theory, pushing the community to reconsider infrastructure and review processes. The release candidate is now available for testing via kernel.org, with the final stable 7.1 expected in approximately two weeks.
Expert Reaction
“This confirms what many of us suspected: the kernel is growing faster than ever before,” said Dr. Elena Voss, a kernel security researcher at the Linux Foundation. “Maintainers will need to adapt their workflows to handle the influx, or we risk longer review cycles and potential regressions.”
Voss noted that the increase is not limited to sheer volume; complexity–measured by cross‑subsystem interactions–is also rising. “Every new driver or feature adds maintenance overhead, and with the current pace, automation tools like static analysis and CI/CD will become critical,” she added.
What This Means
- Increased Testing Load: Three release candidates may not be enough; future cycles could extend to four or five RCs.
- Infrastructure Strain: Build and test servers will need scaling to accommodate larger patch sets without timeouts.
- Potential for Integration Conflicts: More patches mean higher probability of merge conflicts, requiring closer coordination among subsystem maintainers.
- Long-Term Sustainable Development: The kernel project may need to revise its release cadence or adopt selective backporting to keep stable tree updates manageable.
For end users, the immediate impact is minimal—Linux 7.1 will boot on the same hardware as 7.0. However, the “new normal” of larger releases places greater emphasis on thorough testing before deployment, especially for enterprise distributions that often rely on long‑term support kernels derived from these mainline versions.
Outlook
Torvalds has historically resisted calls to slow down development, arguing that kernel quality is maintained by rigorous review, not arbitrary caps on code size. With 7.1-rc3 reinforcing the trend, the Linux community faces a pivotal moment: either scale up review resources or accept that future releases will be larger and less frequent. The discussion is expected to intensify during the upcoming Linux Plumbers Conference.
Stay tuned for the final 7.1 release and subsequent analysis of its long‑term implications for the kernel ecosystem.