Linux kernel reviewer steps down from memory management duties due to influx of AI slop patches

Lorenzo Stoakes has announced he is stepping down from several of his memory management duties in the Linux kernel, citing an overwhelming volume of AI-generated patch submissions. Stoakes made the announcement in a thread on the Linux kernel mailing list. He will leave the core, reclaim, Rust, THP (Huge Pages), and miscellaneous sections of the kernel memory management area. He is staying on for his remaining duties, including KVM.

Stoakes described the departure as amicable, and he did not appear angry or bitter about the situation. He attributed his decision to mounting pressure on his inbox. He said he will wrap up the patch series he is currently working on and will occasionally pitch in regardless of his reduced role.

The underlying cause, according to Stoakes, is the AI wave, which he said has been horrible and is getting significantly worse. He described a progression in which he first saw slop once in a while, then at least once a week, then every few days. Nowadays, he said, it is pretty much half of what he sees, if not more.

Stoakes's concerns are not new. Back in July, he had already raised concerns about the recent wave of slop in memory management. He said at the time that the amount of time wasted on AI slop was already too much and that the community was only at the start of it. Even as recently as a month ago, he said what kills the project is having 1,000 slop submissions that 2 or 3 people have to do something with.

The situation reflects a broader tension in the open-source community, where AI-assisted programming has been both a boon and a curse. The open nature of projects means anyone can report a bug, fix one, or add functionality. That same openness means anyone can contribute, and open-source projects rarely have the manpower or funds to keep code up to date, much less handle large volumes of low-effort AI output.

Linus Torvalds, creator and headmaster of Linux, has taken a pro-AI stance. His position is supported by the speed of additional contributions and by the fact that bots often do not make mistakes that even seasoned developers do. The topic has been the subject of much LKML discussion, and the current stance is that AI-assisted code commits do not need to be marked as such. The problem has arguably become one of filtering, which appears to be what Stoakes grew weary of.

More software news from TechManNews.