# Linux kernel MM reviewer Lorenzo Stoakes steps back citing AI-generated submission flood

> **Key takeaway:** Long-time Linux memory management reviewer Lorenzo Stoakes is relinquishing review duties for MM and Rust-for-MM code because AI-generated patch volume has made reliable review outside his direct maintenance areas unsustainable.

**Published:** 2026-11-13T03:56:24+00:00 
**Source:** TechPowerUp 
**Category:** open-hardware 
**Canonical URL:** https://fosswire.org/news/linux-kernel-mm-reviewer-lorenzo-stoakes-steps-back-citing-a.html 

## Summary
Lorenzo Stoakes, a veteran contributor and reviewer in the Linux kernel's memory management subsystem, has announced he is stepping away from broad review responsibilities due to a surge of AI-generated code submissions. In a patch series announcement, Stoakes stated he lacks the bandwidth to offer reliable review except in areas he directly maintains, and has rerouted patches to other maintainers including David, Andrew, Alice, and Danilo. This development follows a Linux Foundation finding that 25% of incoming pull requests are considered "AI slop," and comes after Linus Torvalds reportedly shifted toward embracing AI-generated contributions in his own work and encouraging others to do so.

Stoakes' departure from MM and Rust-for-MM review duties represents a concrete loss of experienced maintainer capacity in one of the kernel's most critical and complex subsystems. The move highlights a growing tension between AI-assisted contribution tools and the finite review bandwidth of human maintainers, with implications for code quality and subsystem sustainability in upstream Linux development.

## Maintainer attrition and AI submission pressure in kernel MM
- **Memory management subsystem:** Stoakes was a reviewer for the Linux kernel memory management (MM) code, responsible for evaluating patches to virtual memory, page allocation, and related core kernel infrastructure before they reach subsystem maintainers.
- **Rust-for-MM domain:** Stoakes specifically cited stepping back from reviewing Rust code in the Linux memory management domain, an area where Rust is being incrementally introduced for memory safety improvements.
- **Patch rerouting:** Stoakes separated his pending patches by target maintainer—David, Andrew, Alice, and Danilo—explicitly redistributing review load rather than continuing to serve as a general MM reviewer.
- **AI throughput cited as cause:** Stoakes directly attributed his decision to "the current throughput in the kernel resulting from AI-generated series," stating this volume made his inbox unmanageable and reliable review impossible outside his direct maintenance scope.
- **Context of Torvalds' position shift:** The article notes this follows Linus Torvalds moving from caution toward acceptance of AI-generated code, including in his own contributions and public encouragement for developers to embrace AI tools.

## Why it matters
The loss of an experienced MM reviewer to AI-driven volume pressure signals a potential inflection point for Linux kernel maintenance sustainability, as core subsystems rely on deep expertise that cannot be replicated by automated review tools. For Linux distributions, enterprise kernel vendors, and embedded systems depending on stable memory management, this raises concerns about review thoroughness and the risk of maintainer burnout cascading through other critical subsystems. The incident also provides a concrete data point in the broader debate over AI coding agents in open-source governance, contrasting with projects like KDE that are drafting explicit guidelines against unreviewed AI contributions.