As the number of LLM-generated patches in my inbox increases, I am starting to experience the sort of maintainer stress that has long been predicted. But there's another aspect of this that has recently crossed my mind.
Just over a week ago, a new personality showed up with a whole pile of machine-generated patches claiming to fill in our memory-management documentation. A few reviewers had some sharp questions, the response to which has been ... silence. This person doesn't seem to have cared enough about that work to make an effort to get past the initial resistance.
Once upon a time, somebody who had produced many pages of MM documentation would be invested enough in that work to make at least a minimal attempt to defend it.
Kernel developers often worry that a patch submitter will not stick around to maintain the code they are trying to push upstream. Part of the gauntlet of getting kernel patches accepted can be seen as a sort of "are you serious?" test.
When somebody submits a big pile of machine-generated code, though, will they be *able* to maintain it? And will they be sufficiently invested in this code, which they didn't write and probably don't understand, to stick around and fix the inevitable problems that will arise? I rather fear not, and that does not bode well for the long-term maintainability of our software.
@corbet It will be interesting to see how the use of the Assisted-by tag develops. I'm sure not everyone uses it. And if it changes the reception of a patch to be negative, surely people will be less forthcoming about LLM usage too. And, of course, a contribution based on a lie is not a great way to build trust either.
I also see trivial patches with Assisted-by that make me think, why? Couldn't you have done this yourself and learned something in the process.
@jani People are clearly not using the Assisted-by tag; I've seen a lot of examples of that in recent days. In many cases people seem to be unaware of the rules. The human inclination to not read our documentation continues, but it appears that the LLMs don't bother to read it either.
@corbet @jani Assisted-by is optional currently (not a rule). Perhaps it is time to flip this to being required? Making it optional for not even a whole release cycle... 😭
@kees @corbet @jani tbh I think Assisted-by for an LLM tracking down bugs etc. is not worthwhile.
But for entire series, clearly that's required.
There's https://origin.kernel.org/doc/html/latest/process/generated-content.html which I pushed very hard to get updated to add the last few paragraphs.
But it's not quite the same as a rule that's adopted by maintainers I guess...
Of course bad actors won't necessarily read docs.
But there are 'helpful' people who would if pointed to them.
Which was what I was trying to tell Linus when he bit my head off on that thread :)
Kernel Guidelines for Tool-Generated Content — The Linux Kernel documentation
@ljs @kees @corbet @jani Hmm. How did you get that
origin.kernel.org domain? Did something redirect you there?
The Linux Kernel Archives