Linux 7.0-rc4 Released: Torvalds Suspects “New Major Number” Effect Is Driving Larger-Than-Normal Candidates

Linux 7.0-rc4 Released: Torvalds Suspects “New Major Number” Effect Is Driving Larger-Than-Normal Candidates

The fourth release candidate of the Linux 7.0 kernel arrived on March 15, 2026, continuing a pattern of above-average commit volumes that Linus Torvalds attributes not to instability, but to developer enthusiasm around the new major version number.

Linus Torvalds tagged Linux 7.0-rc4 on Sunday, March 15, 2026, posting the announcement to the Linux Kernel Mailing List. The release followed a week that began quietly before a surge of late submissions — a networking subsystem pull on Thursday, followed by a wave of additional patches on Friday — pushed the final commit count well above what is typical for a fourth release candidate.

So last week looked very calm — for a few days. Then Thursday hit with the networking pull. And then on Friday everybody else decided to send in their work for the week, with a few more trickling in over the weekend. End result: what had for a short few days looked like a nice calm week turned into another “bigger than usual” release candidate.

— Linus Torvalds, Linux Kernel Mailing List, March 15, 2026

A Pattern Across the Entire 7.0 Cycle

The elevated size of rc4 is not an isolated event. rc1 came in at a fairly normal 11,500 commits (excluding merges), but rc2, rc3, and now rc4 have all run above historical averages for their respective stages in the development cycle. Torvalds initially wondered whether an extra week in the previous release cycle was the cause, but by rc4 he had developed a different theory.

I’m starting to suspect it’s the psychological result of “hey, new major number” — and people are just being a bit more active as a result.

— Linus Torvalds, Linux Kernel Mailing List, March 15, 2026

It is worth noting that the version number jump from 6.x to 7.0 carries no architectural significance. Torvalds made clear when announcing Linux 7.0 in February that the bump was a practical naming decision — minor version numbers were approaching 20, which is the informal cap the project uses to avoid misleading version comparisons. The kernel’s interfaces and behavior remain stable across major versions.

What rc4 Actually Contains

Despite the higher-than-usual commit count, Torvalds was clear that the actual code changes are benign. Selftest updates account for a noticeable portion of the diffstat, and the kernel diffs themselves are spread across many small, unrelated patches rather than representing any large structural change.

Several notable technical fixes are included in this release candidate:

Scheduler fix (mm/cid): A performance regression in the memory management context ID mechanism that has existed since Linux 6.19 has been resolved. The fix replaces slow counting logic with more efficient structures for associating CIDs and CPUs, which is particularly relevant for large servers and high-process-density systems.

AMDGPU / RDNA4 power fix: An important patch lands for AMD RDNA4 graphics cards addressing an idle and power consumption bug triggered after running compute-intensive workloads — such as AI inference tasks using tools like Llama.cpp. After such workloads, affected GPUs could become trapped in an incorrect power state, causing unnecessary energy consumption. The fix improves the logic for returning the GPU to an idle state.

x86 suspend/resume crash fix: A fix addresses crashes on some systems when resuming from suspend-to-RAM (s2ram). The issue occurred when firmware reactivated x2APIC mode during resume while the kernel was still operating in xAPIC mode, causing crashes on wakeup.

Btrfs fixes: Several patches were merged into rc4 from the Btrfs tree, including fixes for logging new directory entries when parent directory logging involves conflicting inodes, and a correction to avoid unnecessarily holding the device list mutex during zone info queries.

Rust toolchain preparation: rc4 includes preparatory work for compatibility with upcoming Rust language releases, part of the kernel’s ongoing integration of Rust as a supported language for driver development.

Networking volume: The large networking pull from Thursday that triggered the size spike came from the kernel’s networking subsystem — one of the most active trees in the codebase — and includes TCP stack refinements, NIC driver updates, and protocol-level bug fixes.

Development Trajectory and Stable Release Outlook

The Linux kernel development cycle typically runs from rc1 through rc7 or rc8, with Torvalds releasing the final stable kernel once the incoming fix rate drops to an acceptable level. An rc7 endpoint is the most common outcome for a clean cycle; reaching rc8 or beyond generally signals a rougher development run with persistent regressions.

With rc4 landing on schedule, the 7.0 cycle remains healthy. If the cycle ends at rc7, the final stable release will arrive on April 12, 2026. If an additional candidate is required, the release shifts to April 19, 2026. Either way, Linux 7.0 is expected to be a key kernel for major forthcoming distributions, including Ubuntu 26.04 LTS and Fedora 44.

Testers and kernel developers can pull rc4 directly from Torvalds’ Git tree or download the source tarball from kernel.org. As with all release candidates, rc4 is intended for testing and development environments only and is not recommended for production deployment.