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.

  • Hirom ( Hirom@beehaw.org ) 
    link
    fedilink
    arrow-up
    19
    ·
    4 months ago

    Actually proving that C code is correct is not easy.

    Having a human developer manually write code that is less harmful/wrong, and doesn’t require proof, is probably easier.

    • LurkingLuddite ( LurkingLuddite@piefed.social ) BannedBannedBanned from community
      link
      fedilink
      English
      arrow-up
      7
      ·
      4 months ago

      Except a good programmer will have proof, in the form of at minimum manual tests that exercise the exact issue. A good programmer will have automated tests that clearly assert the behavior in question.

      It genuinely boggles my mind when people whine about having to prove what the AI said… THEY SHOULD’VE BEEN DOING THAT THE WHOLE FUCKING TIME in their entire career!