Linux kernel memory-management code reviewer steps down due to influx of AI slop patches — volume of submissions coupled with low manpower forces the step back
So, what if — crazy idea, I know — we dig in our heels and refuse? Could we make this not the start but a quick skip to the end, where we just don’t do all the hellish robot junk and thereby minimise the workload of rolling back to the olden ways?
I agree but I think we’re in a tricky place. The vulnerabilities being found are real, and the pace at which they are now being found is previously unheard of, so in that sense they can’t just be ignored. I’m not a developer but it seems like codebases need to be tightened up as technical debt is finally being called. I don’t have a good answer or suggestion. I’m just a guy who enjoys mixing metaphors and who sees a lot of products that were good enough to ship and build our modern society upon, and suddenly the card foundation demolishing tools have been unleashed.
But are the vulnerabilities real? The reason the slop submissions are such time sinks is that they look plausible enough to not immediately discard, but they turn out to be non issues under further investigation. This is why Curl no longer has a bug bounty. It was just way to tempting for brain addled “coders” with a Claude subscription to see it as a potentialpassive income stream.
Most of what I hear about these AI bots going through a code base and finding hundreds of bugs is reports from AI boosters of not outright marketing claims from the slop merchants themselves, I wonder why they would want to push a narrative of LLMs fixing Swiss cheese software architecture in minutes 🤔
According to the lead Curl developer, the quality of LLM generated reports has gone up quite a lot, to the point where the number of high quality reports is the problem, rather than the number of slop reports: https://daniel.haxx.se/blog/2026/04/22/high-quality-chaos/
However, I doubt that their bug bounty program is ever coming back. As you say, that’ll just attract the people looking for a quick buck, and those are unlikely to care about the quality of their reports
The link I posted is to the Curl maintainer’s own blog, in which he wrote a follow-up to his earlier post about shutting down their bug bounty program. See also this more recent blog post by the maintainer of Curl, in which he writes that
I personally don’t refer to [vulnerability reports created with the help of AIs] as AI slop because the reports are typically accurate and correct, even if much too wordy. I think “slop” implies that it is wrong, misleading or otherwise bad content.
So, what if — crazy idea, I know — we dig in our heels and refuse? Could we make this not the start but a quick skip to the end, where we just don’t do all the hellish robot junk and thereby minimise the workload of rolling back to the olden ways?
I want to see some projects experiment with a “refundable deposit” model for issues and PRs
If it’s slop, the maintainers get paid adequately to deal with it. If it’s not, it doesn’t cost the human anything in the long run
I agree but I think we’re in a tricky place. The vulnerabilities being found are real, and the pace at which they are now being found is previously unheard of, so in that sense they can’t just be ignored. I’m not a developer but it seems like codebases need to be tightened up as technical debt is finally being called. I don’t have a good answer or suggestion. I’m just a guy who enjoys mixing metaphors and who sees a lot of products that were good enough to ship and build our modern society upon, and suddenly the card foundation demolishing tools have been unleashed.
But are the vulnerabilities real? The reason the slop submissions are such time sinks is that they look plausible enough to not immediately discard, but they turn out to be non issues under further investigation. This is why Curl no longer has a bug bounty. It was just way to tempting for brain addled “coders” with a Claude subscription to see it as a potentialpassive income stream.
Most of what I hear about these AI bots going through a code base and finding hundreds of bugs is reports from AI boosters of not outright marketing claims from the slop merchants themselves, I wonder why they would want to push a narrative of LLMs fixing Swiss cheese software architecture in minutes 🤔
According to the lead Curl developer, the quality of LLM generated reports has gone up quite a lot, to the point where the number of high quality reports is the problem, rather than the number of slop reports: https://daniel.haxx.se/blog/2026/04/22/high-quality-chaos/
However, I doubt that their bug bounty program is ever coming back. As you say, that’ll just attract the people looking for a quick buck, and those are unlikely to care about the quality of their reports
That is not what the maintainer of curl said, lmao
This article explains the actual situation.
The link I posted is to the Curl maintainer’s own blog, in which he wrote a follow-up to his earlier post about shutting down their bug bounty program. See also this more recent blog post by the maintainer of Curl, in which he writes that