← Back to Latest

Linux 7.2 Ships Cache-Aware Scheduling as Torvalds Calls AI Contributions 'The New Normal'

Linux 7.2 was released on Sunday, August 16, 2026, bringing one of the most anticipated performance features in years to the mainline kernel. The headline is Cache-Aware Scheduling — a modification to the task scheduler that co-locates tasks sharing data within the same Last Level Cache domain, reducing cache misses and avoiding unnecessary data movement between parts of the CPU. Linus Torvalds shipped the release despite calling the final week "the new normal" in the AI-contribution era. The Debian AI ballot also opened its voting period the same week.

The release followed seven release candidates and roughly two months of development. Kernel.org now lists Linux 7.2 as the latest mainline release, with the merge window for Linux 7.3 already open — 40 pull requests queued as of the week of August 23.

Cache-Aware Scheduling: What It Does

The new scheduler modifies how the kernel places tasks on CPU cores. When threads work on related data, placing them inside the same cache domain can reduce cache misses and avoid moving data unnecessarily between parts of the CPU. On modern multi-core systems with complex cache hierarchies, that locality matters — a lot.

The feature is the headline because it is the performance improvement the community has been waiting for since the 6.x era. Cache-aware task placement is not a new idea in operating system design, but implementing it in the Linux scheduler in a way that works across diverse hardware topologies — from server-grade systems with deep cache hierarchies to embedded chips with shallow ones — is a non-trivial engineering problem. Linux 7.2 is the first mainline kernel to ship it.

The rest of the release is substantial. Linux 7.2 also includes the Intel-developed USB4STREAM protocol, various Intel and AMD hardware driver improvements, and AMDGPU HDMI 2.1 FRL support. The combination of scheduling, storage performance, graphics, networking, virtualization, RISC-V, and Apple Silicon improvements makes 7.2 one of the broader releases in recent memory.

Torvalds on AI Contributions: 'The New Normal'

The most-discussed line from the 7.2 release cycle was not about code. It was about the process. Torvalds described AI-generated contributions as "the new normal" for kernel development — something he has to accommodate rather than resist. His full remark, reported in theWeek 34 roundup, was candid: if he delayed releases waiting for all AI-generated submissions to be perfect, "we'd probably never have a release at all."

The admission matters because it is a public acknowledgment from the kernel's creator that AI-generated contributions are now materially affecting the kernel's development velocity and review burden. The community's response is still evolving. The Debian AI ballot — more on that below — is one response. Torvalds' acceptance is another. The two may diverge significantly.

"If I delayed releases for that reason we'd probably never have a release at all," Torvalds wrote — a candid admission that AI-generated contributions are now materially affecting the kernel's development velocity and review burden.

The context is important. Kernel development has always had a high bar for patch quality, and the review process is one of the reasons the kernel has remained secure and stable at scale. AI-generated patches — particularly those generated by large language models trained on public kernel code — can look correct at a glance and contain subtle errors that are expensive to catch. The review burden increases faster than the patch volume when a fraction of submissions require extra scrutiny.

Whether that is a temporary growing pain or a permanent shift in how the kernel is developed is the question the community is now living with. Torvalds' framing — accommodate, don't resist — is one answer. Debian's answer, via the ballot, is another.

The Debian AI Ballot Opens

The Debian General Resolution debate that was covered in the July 26 roundup moved from discussion to decision the week of August 23: the official ballot opened. Debian developers are now voting on how AI-generated code and content can be used in building the operating system.

The options before voters range from an outright ban on AI-generated contributions to a disclosure-and-allow approach with strict labelling requirements. The ballot closes in early September. The result will be one of the most consequential policy decisions in Debian's 33-year history — and whatever Debian decides, it will influence how other major Linux distributions think about the same question.

The timing is notable. Torvalds this week described AI contributions as "the new normal" for kernel development. Debian is asking its developer community the same question and getting a democratic answer. The two responses may diverge significantly — and that divergence itself is data about how different parts of the open source ecosystem are thinking about the same problem.

Steve French Stepping Back from CIFS/SMB3

Steve French stepped back from his CIFS/SMB3 maintainer role of 24 years the same week the 7.3 merge window opened. French was a longtime IBM engineer before joining Microsoft in 2018 to work on Azure Storage. He continued as the upstream maintainer of the CIFS kernel code, as well as KSMBD — the newer in-kernel SMB server implementation — from within Microsoft.

A merged kernel patch names Paulo Alcantara and Namjae Jeon as the new co-maintainers for CIFS/SMB3. The transition is orderly and the subsystem is in good hands. But the nature of the departure — health reasons — is sobering. French spent 24 years maintaining the code that lets every Linux system talk to Windows file servers, NAS devices, and Azure storage. The community expressed deep gratitude across mailing lists, social media, and the kernel's own commit messages.

The timing — right as the 7.3 merge window opened — is coincidental, but it lands at a moment when the kernel community is already thinking about continuity, contribution, and the human beings behind the code.

Firefox 154, Proton 11.0-2, and the Broader Open Source Landscape

Mozilla released Firefox 154 on August 18, 2026. Highlights include a new "Manage AI" quick action in the address bar that makes it easier to open the AI section of Settings, support for clearing and updating cached favicons when performing a hard reload, and the ability to highlight selected text in PDFs like in normal web pages.

Valve released Proton 11.0-2 with fixes for Helldivers 2, Diablo IV, Marvel Rivals, Forza Horizon, Crysis 2 Remastered, and more. Proton 11.0-2 is a targeted maintenance release for the 11.0 series, addressing compatibility regressions and gameplay issues. Helldivers 2 — one of the most-played titles in the Steam gaming community and one that has had an on-again/off-again relationship with Proton — is restored to full playability in this update.

Wine 11.16 ships with VA-API hardware video decoding, Mono 11.3 with ARM64 support, improved ARM64EC exception handling, and 35 bug fixes. Go 1.27 continues the language ecosystem's steady march.

Seven stable kernel versions were released in a single week — a dense patch cycle. 266 stable kernels have been released in total, each containing another set of important fixes. Among them, eCryptfs saw a number of bug fixes for Linux 7.3, with several dealing with potentially malicious data — some vulnerabilities dating back to the 2006 introduction of eCryptfs. The fixes land in 7.3, but backports for active stable kernels are expected.

A GTK app recoloring tool called Rewaita made an appearance in the open source news — a delightful discovery from It's FOSS that makes it easy to recolor GTK and LibAdwaita apps with popular palettes, custom colors, and visual effects.

What to Watch

Linux 7.3-rc1 is expected August 30, 2026, with the final release in mid-to-late October. The merge window is open with 40 pull requests already queued. Cache-Aware Scheduling will be one of the features to watch in 7.3 — not because it will change in 7.3, but because real-world performance data from 7.2 deployments will start feeding back into the scheduler's tuning.

The Debian AI ballot result — expected in early September — will set a policy direction for one of the largest Linux distributions. Whether that direction is a ban, a disclosure requirement, or something in between, it will influence how other distributions approach the same question. The Torvalds "new normal" framing and the Debian ballot are two different institutional responses to the same phenomenon — and the tension between them is the story to watch.

And Steve French's departure after 24 years is a reminder that the kernel is built by human beings with health and limits. The warm community tribute this week reflects how deeply individual contributors shape the software the world depends on — a point that does not change regardless of how AI contributes to the process.

Related Articles