Linux Kernel Becoming a Slopfest - Part 3 - Besieged by LLM Bots, Now Hiding Behind a Wall of JavaScript

The Linux kernel's git.kernel.org repository is being overwhelmed by LLM-generated bot traffic, forcing the site to serve a JavaScript wall before users can reach kernel commit pages, according to the third installment of TuxMachines' "Linux Kernel Becoming a Slopfest" series published September 18, 2026. The report follows the series' earlier parts on September 15 and 16, and cites a prior TuxMachines account of LLM slop attacking the Linux kernel on August 30, 2026. The article says real names of real people sit behind recent commits that may be LLM slop, and that dozens of repositories go into making a single kernel, complicating any per-repo "shame list" of high-scoring sloppers.

Linux Kernel Becoming a Slopfest - Part 3 - Besieged by LLM Bots, Now Hiding Behind a Wall of JavaScript The series began 3 days ago Part 1 https://techrights.org/n/2026/09/15/Linux Kernel Becoming a Slopfest Part 1 At the Beginning Torval.shtml , Part 2 https://techrights.org/n/2026/09/16/Linux Kernel Becoming a Slopfest Part 2 Bribes From Slop Pusher.shtml and has since then spilled over to other sites, but all the important points will remain here in the "core" series that's also how we covered GitHub fraud, leading up to SLAPPs https://techrights.org/n/2026/09/11/Microsoft GNOME 9 11.shtml . Earlier in the week we thought of downloading the latest kernel git file/s, unpacking it, searching for "assisted by", then sorting the list and reducing the output to a list of serial sloppers who contaminate Linux, eventually making a "shame list", maybe tracing that back to employers and aggregating across staff paraphrasing IRC . Some people in our community supported this idea no issue related to ethics of "shame lists" and urged us to go ahead and do that. Going to git.kernel.org https://git.kernel.org/ over HTTPS, this is what I get: kernel.org, made by slop bots, hammered by bots too http://news.tuxmachines.org/n/2026/08/30/LLM Slop Attacking Linux Kernel.shtml Due to de facto DDoS http://news.tuxmachines.org/n/2025/12/26/Arch Linux Website Hit by DDoS and Temporarily Limited to IPv6.shtml . It's a motif now, isn't it? Should we take such a status quo for granted? After some "JavaScript games" I finally get some JavaScript-free actual page: Who knows how many of those recent commits are LLM slop. There are real names of real people behind such slop and not all of them offer a disclosure of their misuse of "Plagiarism Engines" https://techrights.org/n/2026/05/28/LLMs Are Not Much More Than Plagiarism Engines.shtml to obfuscate other people's code RMS has just commented on that https://techrights.org/n/2026/09/17/What s Wrong with Microsoft s GitHub New Article by Jacob Bachm.shtml or basically make it seem plausible and original. "It's not just one repository," an associate points out, as "there are dozens which go into making a single kernel..." So there can be a per-repo repository sloppers shame list with "high scorers", plus totals for all repos combined. █ top