Linux kernel embraces sloppy AI code, obscuring chatbot commits
| Source: Mastodon | Original article
The Linux kernel now incorporates AI-generated code and has concealed commits related to a chatbot, sparking debate over transparency.
Linux’s core development process has taken a decisive turn toward AI‑generated code, and the community is now actively concealing the origin of those contributions. Earlier this month the kernel maintainers published a new “AI code policy” that bans what they label “AI slop” – low‑quality, indiscriminately generated patches – while formally approving the use of GitHub Copilot for legitimate assistance. The policy stresses that developers remain responsible for any bugs, regardless of whether a chatbot supplied the code.
The shift follows a series of recent moves that signal a tightening of AI governance in the project. In mid‑May, Linus Torvalds warned that AI‑generated bug reports were flooding the kernel’s security mailing list, prompting a rewrite of the official security documentation. A week later, the community released a playbook for shipping AI‑assisted changes, outlining how to integrate chatbot output into the existing review workflow without compromising the project’s standards.
What sets the latest development apart is the practice of “hiding” chatbot commits. Maintainers are now stripping or obfuscating the metadata that would reveal a patch’s AI origin, a step that has drawn criticism from some developers who argue it undermines transparency. The move also coincides with reports that AI‑powered crawlers are consuming disproportionate compute resources on the kernel’s repositories, further straining the infrastructure.
Why it matters is twofold: first, the kernel’s reputation for rigorous peer review could be jeopardised if low‑quality AI code slips through unnoticed; second, the hidden‑commit approach raises governance questions about accountability in open‑source projects that increasingly rely on machine assistance.
Going forward, observers will watch how the policy is enforced and whether the community revises its stance on disclosure. The next indicators will be the volume of AI‑tagged patches accepted for inclusion, any adjustments to the “AI slop” definition, and how the kernel’s security mailing list adapts to the continued influx of AI‑generated reports. As we reported on 15 October, developers have already begun dropping obligatory AI‑tool usage confessions, suggesting a broader trend toward opacity that could reshape contribution norms across the open‑source ecosystem.
Sources
Back to AIPULSEN