Linux 7.1 RC2 Released: AI Has Permeated Kernel Development

Linus Torvalds released the second release candidate of the Linux 7.1 kernel on Sunday, May 3, 2026, calling the overall state of development “fairly normal” — a reassuring signal that the kernel is on track to ship on schedule. The release follows two weeks after Linux 7.0 arrived on April 12, opening the merge window for the next cycle.

For observers watching the kernel’s development cadence, the headline of this particular RC is not a specific bug fix or a headline feature — it is something subtler and more systemic: the growing, near-invisible fingerprint of AI tooling across the codebase.

The KVM Oddity: Big Numbers, Modest Meaning

At first glance, the raw diff statistics for Linux 7.1-rc2 look alarming. Half of the entire patch volume consists of changes to KVM (Kernel-based Virtual Machine) self-tests. Torvalds was quick to contextualise this: the changes are almost entirely cosmetic renaming, aligning variable and type names in the self-test code with the kernel’s established naming conventions.

The raw diffstat doesn’t look normal, with half of the diff being to the kvm selftests, but that’s pretty much entirely due to just renaming… it all looks big and strange, but you should just ignore that oddity.

— Linus Torvalds, Linux 7.1-rc2 announcement

Once that renaming effort is set aside, Torvalds confirmed the remainder of the update looks exactly as a healthy RC2 should: roughly half driver fixes, with graphics and networking drivers leading as usual, and the rest distributed across architecture code, filesystems, and kernel internals.

AI Tooling: A Pattern Now Confirmed Across Releases

Torvalds noted something that developers have been whispering about for months: the sheer volume of patches flowing into the kernel appears to be rising, and he suspects AI development tools are a significant factor. This is not speculation — he observed the same pattern during Linux 7.0’s development cycle, and Linux 7.1-rc2 appears to be continuing the trend.

The implication is significant. Kernel development has long been the domain of highly specialised, deeply experienced engineers. The idea that AI coding assistants — tools designed for productivity across all levels of programming — are now influencing patch volume in the Linux kernel suggests that the technology’s reach has extended further than many anticipated.

Driver and Subsystem Fixes

Beyond the statistical noise, Linux 7.1-rc2 delivers a meaningful set of bug fixes. Graphics and networking drivers — the perennial majority of any RC — account for the bulk of non-self-test changes.

On the graphics side, improvements and fixes have landed for older AMD GPU hardware, courtesy of Valve engineer Timur Kristóf, alongside Intel Xe driver workarounds and tuning for next-generation Xe3P graphics. Notably, the release also carries an audio fix for the Steam Deck OLED: the mainline kernel had broken audio support for Valve’s handheld for the past two years, with Valve and handheld-focused distributions carrying their own patches as a workaround. That fix is now mainlined.

Storage and filesystem stability also received attention. The release includes fixes for NVMe authentication and TLS mode exposure — issues that could create unauthorised access risks — as well as corrections to core logic errors in RAID10 array configurations, the rewritten NTFS filesystem driver that debuted in Linux 7.1-rc1, and the ICE network driver stack. These fixes collectively reduce the probability of system crashes in affected configurations.

The sched_ext scheduler extension framework, which has attracted growing interest for AI workload tuning, also received a batch of fixes following increased AI-assisted code review and fuzzing.

Release Timeline: What to Expect

Linux kernel releases typically follow a seven-week RC cycle, with the stable release shipping in the eighth week. An RC8 is possible — and would delay the final release by one additional week — but Torvalds indicated no current reason to expect that outcome.

The primary signal of a delayed release would be a deterioration in stability over coming weeks, forcing additional testing. Torvalds does not expect this to occur based on the current state of the codebase.

Why This Release Matters

For users running cutting-edge hardware, each new kernel release is a meaningful milestone: support for new devices, refinements to existing drivers, and security patches that may not reach older stable kernels for some time. Linux 7.1 builds on a 7.0 cycle that introduced substantial changes, and the steady cadence of RC releases is the clearest possible sign that the kernel community remains healthy and productive.

The more subtle story, however, belongs to AI. For decades, the Linux kernel was a space where AI felt entirely abstract — a topic discussed in research papers, not a tool shaping commit logs. Linux 7.1-rc2 suggests that era is over. Whether through code generation, review automation, or fuzzing, AI tooling has made its way into the deepest layers of the software stack. Torvalds is not alarmed — but he is paying attention.

Linux 7.1-rc2 is available for testing now from kernel.org and Linus Torvalds’s public Git tree. Production systems should wait for the stable release.