288
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Oct 2026
288 points (90.7% liked)
Technology
88814 readers
6193 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
Cool assumption. But pretty sure it's not how things work at all but sounds great...
What actually happens is that you have a long list of multiple maintainers reviewing , and multiple branches for testing, and multiple layers of review too.
https://www.kernel.org/doc/html/next/process/maintainers.html . See that long list of maintainers for a start.
The actual policy is that everything ends up getting reviewed by a human. If I post a patch, it doesn't go straight to master
If it's not being properly tested and maintained, it gets dropped irrespective of what it is (remember devfs?)
Also, I'm not sure about the kernel specifically, but on projects I submitted code to, they often wanted complex patches broken down if possible.
Yes this means the review process is working. What is important to track is if LLM code causes a disproportionately large number of reviews or reviews that take longer because whoever generated the code doesn't actually know what it is doing. Hopefully not the case here but it does happen a lot with LLM coding.
Linus secretly understands nothing about the Linux kernel
XZ Utils made it past all those checks with malicious code from a human.
If they’d been more careful with their tarball commits it probably would have made it into the final and commercial distros.
It made into Homebrew for instance.
Correct me if I'm wrong, but that's not the kernel...
You are correct, also has nothing to do with AI, just malicious actors.
Yep. And the kernel did actually have a backdoor attempt at some point. And it was noticed too https://www.infoq.com/news/2013/10/Linux-Backdoor/