From: Jori Koolstra <jkoolstra@xs4all.nl>
To: Theodore Tso <tytso@mit.edu>, Andreas Dilger <adilger@dilger.ca>
Cc: Jonathan Corbet <corbet@lwn.net>,
Greg KH <gregkh@linuxfoundation.org>,
Jeff Layton <jlayton@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Justin Stitt <justinstitt@google.com>,
Lorenzo Stoakes <ljs@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Carlos Maiolino <cem@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Brian Foster <bfoster@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
David Disseldorp <ddiss@suse.de>, Mark Brown <broonie@kernel.org>,
Jani Nikula <jani.nikula@intel.com>, Jens Axboe <axboe@kernel.dk>,
David Hildenbrand <david@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
"Christian Brauner (Amutable)" <brauner@kernel.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Documentation: remove the requirement for LLM attribution
Date: Fri, 3 Jul 2026 13:50:33 +0200 (CEST) [thread overview]
Message-ID: <692060611.3935473.1783079433726@kpc.webmail.kpnmail.nl> (raw)
In-Reply-To: <akcji3OuxXz3FqSD@mit.edu>
> Op 03-07-2026 04:57 CEST schreef Theodore Tso <tytso@mit.edu>:
>
>
> On Thu, Jul 02, 2026 at 12:46:19PM -0500, Andreas Dilger wrote:
> > It would make sense IMHO to address the ignorance in the most expedient manner,
> > namely by telling the *LLM itself* to add this tag when it generates the commit
> > message and/or reviews the code.
> >
> > This could be achieved by adding a statement in "AGENTS.md" in the root of the
> > source tree to this effect, or telling the agent to reference and follow rules
> > in Documentation/process/coding-assistants.rst regarding the Assisted-by: tag.
>
> This presupposes a particular workflow where the developer allows the
> LLM to generate git commits. I don't do that. I'll ask the LLM to
> modify the code, but then I'll generally fix it up --- very often by
> hand because I can edit the sources than entering a prompt and waiting
> for the LLM to figure out how to make the change. I'll often run the
> test cases myself, since if it takes 24 hours of VM time, and 2 hours
> of wall clock time, I'm going to kick off the regression tests myself,
> and verify the test results.
>
> And I almost always write the commit description myself. So when I
> say, "Assisted-by" it literally is "Assisted by". It is not "vibe
> coded where the LLM generates thousands of lines of code that the
> human being doesn't understand before sending ta pull request." And
> that's probably why you'll see people asserting that LLM generated
> code can't possibly be accepted due to copyright reasons. There's a
> big difference between asking an LLM to modify already existing code
> to add a feature, or to fix a bug, and to vibe code a new OS from
> scratch. One is far less likely to be a copyright violation than the
> other.
>
> - Ted
Just curious if you know about any quantifiable insight into this. I do know
that the issues also plays up in smaller requests. I once asked an LLM to
give me boilerplate for a FUSE fs, and it took almost verbatim the example
hello.c from the repo (which I only recognized because I had looked at that code)
but stripped the copyright info. And this is only like 100 lines of code or so.
Best,
Jori.
next prev parent reply other threads:[~2026-07-03 11:50 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 14:32 [PATCH] Documentation: remove the requirement for LLM attribution Jeff Layton
2026-07-02 14:53 ` Laurent Pinchart
2026-07-02 14:58 ` Lorenzo Stoakes
2026-07-02 15:02 ` Jeff Layton
2026-07-02 15:07 ` Lorenzo Stoakes
2026-07-02 14:57 ` Lorenzo Stoakes
2026-07-02 15:28 ` Laurent Pinchart
2026-07-02 15:36 ` Lorenzo Stoakes
2026-07-02 15:44 ` Laurent Pinchart
2026-07-02 15:07 ` Greg KH
2026-07-02 15:13 ` Jonathan Corbet
2026-07-02 15:20 ` Lorenzo Stoakes
2026-07-02 18:46 ` Andreas Dilger
2026-07-03 2:57 ` Theodore Tso
2026-07-03 11:50 ` Jori Koolstra [this message]
2026-07-03 16:12 ` Andreas Dilger
2026-07-02 15:15 ` Lorenzo Stoakes
2026-07-02 15:33 ` Jori Koolstra
2026-07-02 15:37 ` Lorenzo Stoakes
2026-07-02 15:36 ` Laurent Pinchart
2026-07-02 15:57 ` Jeff Layton
2026-07-02 16:13 ` Laurent Pinchart
2026-07-02 16:19 ` Greg KH
2026-07-02 16:32 ` Laurent Pinchart
2026-07-03 6:37 ` Greg KH
2026-07-03 7:23 ` David Hildenbrand (Arm)
2026-07-03 7:30 ` Greg KH
2026-07-03 7:33 ` David Hildenbrand (Arm)
2026-07-03 11:42 ` Theodore Tso
2026-07-03 11:53 ` Laurent Pinchart
2026-07-03 12:04 ` Jori Koolstra
2026-07-06 8:44 ` Mauro Carvalho Chehab
2026-07-02 16:48 ` Jeff Layton
2026-07-02 16:50 ` Lorenzo Stoakes
2026-07-02 21:17 ` Boris Burkov
2026-07-02 23:17 ` SJ Park
2026-07-03 7:05 ` David Hildenbrand (Arm)
2026-07-03 13:12 ` Lorenzo Stoakes
2026-07-03 16:32 ` Laurent Pinchart
2026-07-03 18:22 ` David Hildenbrand (Arm)
2026-07-07 9:20 ` Lorenzo Stoakes
2026-07-07 9:49 ` David Hildenbrand (Arm)
2026-07-07 9:55 ` Lorenzo Stoakes
2026-07-07 13:29 ` David Hildenbrand (Arm)
2026-07-07 15:10 ` Lorenzo Stoakes
2026-07-07 17:10 ` Darrick J. Wong
2026-07-07 18:16 ` Lorenzo Stoakes
2026-07-07 10:01 ` Geert Uytterhoeven
2026-07-07 13:31 ` David Hildenbrand (Arm)
2026-07-07 12:40 ` Laurent Pinchart
2026-07-07 13:28 ` David Hildenbrand (Arm)
2026-07-07 14:18 ` Laurent Pinchart
2026-07-07 14:59 ` Lorenzo Stoakes
2026-07-07 15:05 ` Laurent Pinchart
2026-07-07 18:53 ` Christian Brauner
2026-07-07 18:55 ` Christian Brauner
2026-07-07 19:03 ` Jonathan Corbet
2026-07-07 19:06 ` Lorenzo Stoakes
2026-07-07 10:15 ` Jori Koolstra
2026-07-07 10:20 ` Lorenzo Stoakes
2026-07-03 18:26 ` David Hildenbrand (Arm)
2026-07-02 23:05 ` SJ Park
2026-07-02 16:11 ` Chuck Lever
2026-07-02 16:14 ` Lorenzo Stoakes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=692060611.3935473.1783079433726@kpc.webmail.kpnmail.nl \
--to=jkoolstra@xs4all.nl \
--cc=adilger@dilger.ca \
--cc=axboe@kernel.dk \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=cem@kernel.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=ddiss@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jani.nikula@intel.com \
--cc=jlayton@kernel.org \
--cc=justinstitt@google.com \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vbabka@kernel.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox