Linux kernel maintainer reports sudden shift in AI-generated bug report quality
Greg Kroah-Hartman, a long-term Linux kernel maintainer, reports a significant change in AI-generated bug reports for the Linux kernel. About a month ago, reports transitioned from what he calls 'AI slop'—obviously wrong or low-quality security reports—to legitimate, useful findings.
The inflection point
Kroah-Hartman notes that 'something happened a month ago, and the world switched. Now we have real reports.' This shift isn't limited to the Linux kernel—he says all open source projects are seeing similar legitimate AI-generated reports. Security teams across major open source projects are informally discussing this change, with everyone experiencing the same transition.
Impact on different projects
The Linux kernel team, being larger and more distributed, can handle the increased volume of reports. Kroah-Hartman states: 'For the kernel, we can handle it. We're a much larger team, very distributed, and our increase is real – and it's not slowing down.' However, he implies smaller projects have less capacity to absorb this sudden flood of plausible AI-generated bug reports.
AI's current role in kernel development
AI is currently showing up more as a reviewer and assistant than as a full author of Linux kernel code, though that line is starting to blur. Kroah-Hartman conducted his own experiment with AI-generated patches: 'I did a really stupid prompt. I said, 'Give me this,' and it spit out 60: 'Here's 60 problems I found, and here's the fixes for them.' About one-third were wrong, but they still pointed out a relatively real problem, and two-thirds of the patches were right.'
He notes that even the working patches still needed human cleanup, better changelogs, and integration work. For 'simple little error conditions, properly detecting error conditions,' AI could already generate dozens of usable patches today.
Tooling response
The increase in AI-generated reports has spurred integration of AI into the kernel's review infrastructure. A key tool is Sashiko, originally developed at Google and now donated to the Linux Foundation. Kroah-Hartman says: 'We need to be able to have an easy way to review some of these patches that come in ways that cut down on our load.' The tool is 'out there, running on almost all kernel patches' and publicly visible, with integration into review tools underway.
📖 Read the full source: HN AI Agents
👀 See Also
Developer Switches from Cursor Composer 2 and Kimi 2.6 to Qwen3.6:35b-a3b for Enterprise Workloads
A developer reports using Qwen3.6:35b-a3b for daily work on a 500-700k LOC enterprise suite, citing better performance than Kimi 2.6 and DeepSeek 4 Pro/Flash, with costs ~$0.08/1M tokens on OpenRouter.
AI Scans 400K Reddit Posts, Uncovers Hidden Ozempic Side Effects Like Menstrual Changes
University of Pennsylvania researchers used LLMs to analyze 400,000 Reddit posts on GLP-1 drugs, uncovering underreported symptoms like menstrual irregularities and chills.
Meta's MCI Tool Captures Employee Interactions for AI Training
Meta is installing tracking software called Model Capability Initiative (MCI) on U.S. employee computers to capture mouse movements, keystrokes, clicks, and occasional screen snapshots for AI model training. The data aims to improve AI's ability to replicate human computer interactions like dropdown menu selection and keyboard shortcuts.
AI Tools May Lead to Homogenized Output in Creative and Development Work
A Reddit user reports that multiple teams using AI tools like ChatGPT, Co-Pilot, and Claude for strategy roadmaps and software development are producing similar outputs with identical buzzword patterns and design structures.