Re: [MAINTAINERS SUMMIT] Annotating patches containing AI-assisted code

[Sasha Levin <sashal@kernel.org>]

On Mon, Aug 11, 2025 at 02:57:30PM -0700, Luck, Tony wrote:
>On Mon, Aug 11, 2025 at 02:46:11PM -0700, Paul E. McKenney wrote:
>> On Fri, Aug 08, 2025 at 10:31:27AM +0200, Krzysztof Kozlowski wrote:
>> > On 05/08/2025 19:50, Sasha Levin wrote:
>> > With AI you do not have to even write it. It will hallucinate, create
>> > some sort of C code and you just send it. No need to compile it even!
>>
>> Completely agreed, and furthermore, depending on how that AI was
>> trained, those using that AI's output might have some difficulty meeting
>> the requirements of the second portion of clause (a) of Developer's
>> Certificate of Origin (DCO) 1.1: "I have the right to submit it under
>> the open source license indicated in the file".
>
>Should the rules be:
>
>1) No submissions directly from an AI agent. The From: line must
>always refer to a human.

We already require that, no?

We have the following in our docs:

         code from contributors without a known identity or anonymous
         contributors will not be accepted. All contributors are required
         to "sign off" on their code

Which requires a real, known, human identity behind the "Signed-off-by"
tag.

I don't think anyone here interperted it differently, but we can maybe
ask the LF legal folks if that's the case (and help us improve it) if
you think that this interpertation is not clear.

>2) The human on the From: line takes full responsibilty for the
>contents of the patch. If it is garbage, or broken in some way
>there's no fall back on the "but AI wrote that bit".

So right now the bigger issue the community has faced from this aspect
is mindless checkpatch/syzbot/etc "fixes".

We already have extensive requirements in the docs that often just get
ignored. Look at submit-checklist.rst, authors must:

1. Test with multiple debug configs.
2. Exercise all code paths with lockdep
3. Test with fault injection.
4. Verify build against linux-next.
5. Code builds cleanly with no warnings.
6. Passes all[yes,no,mod]config builds.
7. Builds on multiple CPU archs.
8. Follows coding style.
9. Keeps checkpatch.pl happy.
10. Checked with sparse.
11. Justifies any violations.

-- 
Thanks,
Sasha