208
Linux's Staging Area To Now Reject LLM-Generated Patches, Except For Real Security Fixes (www.phoronix.com)
submitted 3 months ago by to c/linux@programming.dev
18 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 42 points 3 months ago (8 children)

Nice, I can get behind that policy. LLMs can be useful but only if you assume the output is wrong until proven correct. Using it to find potential threads to pull at makes sense to me but not blindly trusting everything it points out

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 19 points 3 months ago (7 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 4 points 3 months ago (6 children)

    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!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 19 points 3 months ago* (2 children)

    We're talking about different kind of proofs.

    Proving a program is correct requires a formal specification and a formal verification with mathematics and/or formal methods. ie proving the behavior and result perfectly match specification for all possible inputs.

    A test only proves that a program 1) returns the expected output for a specific input, or limited set of inputs, and 2) appears to behave correctly, ie there may be undefined behaviour but they don't cause an immediate crash.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •