Linus Torvalds, the creator of the Linux kernel, has weighed in on a problem that has been quietly growing for months: AI-generated bug reports are piling up faster than maintainers can triage them, and a large portion of them are useless.
Torvalds described the volume as "unmanageable" - a word that carries weight coming from someone who has run one of the most active open-source projects on the planet for over 30 years. The Linux kernel receives thousands of patches, reports, and messages each month. Adding a flood of AI-generated noise on top of that strains a maintainer community that was already stretched.
What Makes AI Bug Reports Different
The core problem isn't that AI tools produce technically wrong output - it's that they produce plausible-looking output that still requires a human to verify. A bug report generated by an AI assistant might cite real function names, real kernel subsystems, and a real-sounding description of a crash. But without the underlying hardware logs, a reproducible test case, or actual debugging work, that report tells a maintainer almost nothing.
Maintainers can't auto-reject reports that look detailed. They have to read them. That's the cost: time and attention, not disk space.
This is a pattern that shows up across open-source projects, not just Linux. Maintainers on projects ranging from Python libraries to security tools have reported a rise in AI-assisted contributions that clear a superficial quality bar while failing a deeper one. The reports are grammatically coherent. They reference the right files. They just haven't been tested or thought through.
The Harder Conversation About AI Coding Tools
Tools like Cursor, Claudee Code](/tools/claude-code/), and Aider have made it genuinely faster for developers to write code and draft documentation. That's real. But the same capability that helps an experienced developer move faster also lets someone with minimal kernel experience generate a three-paragraph bug report in 45 seconds and submit it to the LKML mailing list.
Torvalds' comment puts a name on something maintainers have been absorbing quietly: the submission cost has dropped to near zero, but the review cost hasn't. Every low-effort AI submission shifts work onto volunteers who are already unpaid and often burned out.
The open-source community hasn't settled on how to respond. Some projects are adding explicit AI-contribution policies. Others are considering automated filters. Neither solves the underlying problem, which is that there's no reliable way to distinguish a well-researched AI-assisted report from a two-minute AI dump without reading it.
For developers using AI tools to contribute to open-source projects: the tools are genuinely useful, but the standard is still "would a maintainer's time be better spent on this?" If the answer requires real debugging work first, do that work before submitting.