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.

    • 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."