Note, LLMs are very good at finding suspect “security issues” in kernel code these days. But even with the best of the current and next generation tools, at least 1/3 of the results they generate are flat out wrong or harmful. So, if you think your LLM-found/fixed issue in a drivers/staging/ file is really valid, it’s fine to submit it BUT you must have first tested it on the actual hardware for the driver, and described how you have done so, in order for us to be willing to take the change.

  • mrmaplebar@fedia.io
    link
    fedilink
    arrow-up
    84
    arrow-down
    6
    ·
    2 days ago

    Record time speedrun from “I’m putting my foot down in favor of AI” to “at least 1/3 of patches are flat out wrong or harmful”, eh?

      • balsoft@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        3 hours ago

        Yeah, all other commenters here just didn’t read the article it seems.

        First off, drivers/staging/ exists PRIMARILY as a place for new kernel developers to learn how to get involved in kernel development. It contains loads of “low hanging fruit” with regards to code cleanups and api changes, perfect for new developers to learn the process in a safe and friendly way, with no pressure as no one should be relying on the code in these directories

        <…>

        In other words, drivers/staging/ here is a “gym” that is here to learn and grow your skills with. A LLM is turning into a reasonable tool to do “heavy lifting” for some things but that should only be done by those that have already properly trained their skills to know what type of lifting can be done, and in what way. See this great essay by Bruce Schneier for where he explains this in much better detail."

      • Nalivai@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        9 hours ago

        Just like in a lot of other topics, neutrality doesn’t exist here. If you’re not actively opposing evil, you’re supporting it. As a narrow example, be “neutral” to slop, drown in it immediately.

      • _stranger_@lemmy.world
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        9 hours ago

        Exactly this. Linus doesn’t give a shit if the garbage came from meat or a clanker, he treats all garbage equally.

        If it’s obviously AI, you may get a silent rejection instead of a public beating.

        If it’s not garbage, you may get a change request email!

    • strangemath@lemmy.world
      link
      fedilink
      English
      arrow-up
      45
      arrow-down
      1
      ·
      2 days ago

      It’s easy to not have a problem with AI merge requests when you have a whole team of people filtering out the garbage before it gets to you.

    • MalReynolds@piefed.social
      link
      fedilink
      English
      arrow-up
      22
      arrow-down
      3
      ·
      1 day ago

      It was “I’m putting my foot down in favor of AI” for finding security flaws and triaging issues, not writing code. Shit’s useful for things that can be easily verified, like security flaws, less so (OK, crap) for writing maintainable code in a massive codebase with highly complex interactions.

      • Phoenixz@lemmy.ca
        link
        fedilink
        arrow-up
        12
        arrow-down
        1
        ·
        1 day ago

        AI is a tool, its just that most people seem to not understand that you don’t want to use a screw driver as a hammer

        And before anyone goes crazy about me defending AI, I’m not. At least not the AI we see today with the world destroying data centers and so on. Every tool has its uses, so does AI, its just that the real use cases are highly limited