Linux 7.2 draws 2,652 developers as LLM-driven bug fixes surge
Linux bugs fixed per release over time: >2× rise since 2026-04
The 7.2 kernel, released August 17, is the second-busiest cycle in Linux history: 16,418 non-merge commits from a record 2,652 developers, including 613 first-timers. Nearly 600,000 lines were added. LLM influence is growing — 1,111 commits carry Assisted-by tags, up from 301 in 7.1, and 4,830 commits carry Fixes tags, part of a sharp rise in bug fixes per release.
Accurately tracking commits developed with LLM assistance may turn out not to be possible, but it sometimes feels like the kernel community does not care enough to really try.
- ogoffart
I have noticed the same on my project.
The agent helps a lot to fix bugs. Just point the agents at the bug reports. They do the reproduction, debugging and fixes. We "just" have to review. (Sometimes ask more details and tell we'd prefer another approach.) This makes bug fixing much faster and automated.
And at the same time, it seems we get less bug reports to our library.
I think user just use their agents to code, and agents don't report bugs, they just work it around somehow.
So overall, the open bug count is decreasing. Which somehow feels good.
On the other hand, we get a lot of PR made by other's people agents, which can be a bit overwhelming when it's just a huge code drop. We can't easily review that.
- zdw
Greg KH did a video on the flood of LLM created stuff: https://www.youtube.com/watch?v=NnV_cWeoo5Q , HN thread: https://news.ycombinator.com/item?id=49929391
Which covers how he responds and pushes back on much of this, as well as asking for a patch (not just bug reports)
- 05kqhg
The headline is "Development statistics for the 7.2 kernel", and the last paragraph is highly LLM critical in contrast with the editorialized headline "Linux bugs fixed per release over time: >2× rise since 2026-04", which seems to imply some sort of Mythos bug finding.
From the last paragraph:
"The Linux kernel is aimed at production use, not research or experimentation. But there is currently a massive experiment being run on the kernel's development processes and community."
- jayd16
The major issue with these kinds of blurbs is that there's no control.
Historical numbers are not valid because incentivizes of a well funded entity have changed. It would require an equally well funded push to up the patch numbers without LLMs to really measure the impact in a quantifiable way.
- AmazingEveryDay
Just how massive can the machine-generated amdgpu header files get, it may be time to set some limits.
- dash2
So it seems worth vibecoding a survival analysis for bugs introduced. But not quite a survival analysis because we don't even know the bugs exist until the event of their discovery.... Is there a publicly available dataset for this, with a URL?
- tosti
Heads up for those upgrading to 7.3, I just downgraded my slackware box from 7.3-rc7 to 7.2.10 because /dev/input/events was missing. Keyboard and mouse only worked in the console as a result.
YMMV
- cwillu
Please don't editorialize titles.
(Edit: title has been fixed)