this post was submitted on 16 Oct 2026
119 points (79.6% liked)

Linux

19541 readers
226 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 3 years ago
MODERATORS
 

There appears to be a few bad actors in the Lemmy community spreading ragebait for personal gain

In fact, the same mechanisms added at the beginning to catch bad human written code are the exact same that catch bad AI code

  1. No, the Linux kernel won't use AI to auto approve code for inclusion. And no plans to do so
  2. The Kernel actually has a huge number of maintainers. As part of the process, all patches are reviewed by a human who provide feedback as part of the process, and patches get bounced back and forth multiple time.
  3. Patches don't just magically go straight to master. The maintainers generally have their own branches where it goes to, then it goes to staging trees like Linux-Next. It goes through many eyes, and many tests by the end. The idea that AI code is overrunning the kernel is rediculous
  4. Maintainers also check that the code meets coding guidelines and is written properly, and solves the problem they are trying to solve. Yes, they also ensure the code isn't slop
  5. LLM's though might be used to identify obvious problems (bugs / coding guideline issues) with the code. These don't generate "slop" just find issues
  6. The only thing that matters is the human who submitted the code, as they should be checking the code submitted anyway (including LLM generated code).

Writing bad code isn't something new, and isn't unique to LLM's. Coders (and it seems some "journalists") have been writing slop since computers were invented.

The process hasn't gotten less stringent (probably even MORE stringent as there is an additional set of robotic eyes that can also check), and the same mechanisms that were put in place to catch badly written code 10 years ago, are still there now

you are viewing a single comment's thread
view the rest of the comments
[–] auzy1@lemmy.world 2 points 23 hours ago

Just because an issue isn't reported though, doesn't mean it hasn't been noticed by users.

We often see issues which are discussed in private forums, but were never actually reported to us (which is why we check them all)