Linux filesystem development
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
	 Jori Koolstra <jkoolstra@xs4all.nl>,
	Christian Brauner <brauner@kernel.org>,
	 Linus Torvalds <torvalds@linux-foundation.org>,
	Jonathan Corbet <corbet@lwn.net>, Jens Axboe <axboe@kernel.dk>,
	 David Hildenbrand <david@kernel.org>,
	Jeff Layton <jlayton@kernel.org>,
	workflows@vger.kernel.org,  linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC] coding-assistants: simplify attribution
Date: Thu, 2 Jul 2026 13:53:17 +0100	[thread overview]
Message-ID: <akZeZ9GTjSp1L58S@lucifer> (raw)
In-Reply-To: <a4406124-2d0c-4703-9ee6-174af94d6fd9@kernel.org>

On Thu, Jul 02, 2026 at 02:39:53PM +0200, Krzysztof Kozlowski wrote:
> On 02/07/2026 14:23, Lorenzo Stoakes wrote:
> > On Thu, Jul 02, 2026 at 12:34:34PM +0200, Krzysztof Kozlowski wrote:
> >> On 02/07/2026 10:44, Vlastimil Babka (SUSE) wrote:
> >>> On 7/2/26 10:12, Jori Koolstra wrote:
> >>>> Ah, I still reigniting this discussion again :)
> >>>>
> >>>> What about a combination of what David and Jeff say? The whole point
> >>>> seems to me that the salient information is not that an LLM was used (or
> >>>> are we going to tag Sashiko as well or any other LLM-based code review
> >>>> tool?), but what is was used to do. This information may be relevant for
> >>>> how the review is approached. The latter should perhaps only be in the
> >>>> cover letter and then we can drop the assisted-by tags altogether.
> >>>>
> >>>> The question about enforcement remains.
> >>>
> >>> It's not possible to enforce it. People can deny it if the tag is missing
> >>> and you confront them and even though the submission has many signs of being
> >>> obviously LLM, there is no definite proof. We've seen (likely, as there's no
> >>> proof!) that happen in mm.
> >>>
> >>> Such situation then penalizes those who disclose so obviously they won't. We
> >>> should drop the tag and instead think how we can empower maintainers to be
> >>> able to use their own judgment and deprioritize dealing with what they
> >>> perceive as LLM slop, without fearing consequences of not being properly
> >>> responsible etc, and not rely on any non-enforceable tags for that.
> >>
> >> +1
> >>
> >> I see no benefits of enforcing the tag for these exact reasons. Every
> >> LLM slop will miss the tag. OTOH, seeing reasonable contribution with
> >> the tag makes my spider-senses tingling and causing unnecessary
> >> prejudice. If the contribution is reasonable, how does the tag
> >> information helps me? I trust (or not) the person, regardless what tool
> >> they use.
> >>
> >> And if we think about any future possible copyright issues with LLM
> >> contributions (like if there is ever a ruling that model trained on BSD
> >> data creates BSD-derivative work etc), does that tag anyhow solve it?
> >> Like if that ruling appear we will go through the history and revert the
> >> commits?
> >
> > Why would you take information _away_ from maintainers?
> >
> > You're making every LLM 'accusation' a risk for a maintainer because you might
> > get the 'how dare you accuse me of using an LLM rah rah rah' response.
> >
> > Why not eliminate that in at least some cases?
>
> Because I don't think we will be able to enforce that information,
> therefore it is close to pointless.

'We can't have complete data so let's have no data'

Not sure that's convincing, sorry.

>
> And if you ask about future copyright issues, I simply do not believe
> the tags will matter based on argument (repeating): what are you going
> to do with that information that commit was involving LLM tool which now
> received some copyright-related verdict?

And if undisclosed, but detectable by LLM checks or otherwise evidenced...? Not
sure you can argue 'no point in tags because people don't use them' but also
'copyright issues only with tags'.

Anyway I think this is likely to be a non-issue given global regulatory trends
on this stuff.

>
> >
> > I continue to be baffled at people's opposition adding a single line to emails,
> > or a single little comment on the end of it.
> >
> > I do agree with Vlasta that we need to have a clearer way to just say no (TM) if
> > we strongly suspect an LLM.
>
> This part is not being discussed by me and I think the thread itself is
> not about it.

Well ok on your part, but I think it's clearly part of it, quoting Vlasta:

"instead think how we can empower maintainers to be able to use their own
judgment and deprioritize dealing with what they perceive as LLM slop, without
fearing consequences of not being properly responsible etc, and not rely on any
non-enforceable tags for that."

>
> >
> > I had a very unpleasant experience dealing with blowback for doing that in a
> > _very_ blatant case and I'd rather not repeat it if it's at all possible.
>
> Well, I made here the point already - that blatant blowback and any
> future similar slop will not use any tags, thus the tags do not solve
> that problem.
>
> Basically having the tag solves no problems we experience. The tags are
> worthless in problem solving...

Well in my actual experience of doing review I am finding them useful as a
low-cost way of being able to bring up LLMs.

Some information > no information.

And requiring disclosure makes not disclosing an easier sell. If we drop it then
people will take that as carte blanche to do whatever.

>
> Best regards,
> Krzysztof

Thanks, Lorenzo

  reply	other threads:[~2026-07-02 12:53 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 15:54 [PATCH RFC] coding-assistants: simplify attribution Christian Brauner
2026-07-01 16:08 ` Mark Brown
2026-07-02  7:10   ` Christian Brauner
2026-07-02 11:35     ` Mark Brown
2026-07-01 16:08 ` Jonathan Corbet
2026-07-01 16:12   ` David Hildenbrand (Arm)
2026-07-02  7:11   ` Christian Brauner
2026-07-02  9:51   ` David Disseldorp
2026-07-01 16:10 ` David Hildenbrand (Arm)
2026-07-02  7:27   ` Christian Brauner
2026-07-02  7:46     ` David Hildenbrand (Arm)
2026-07-02  8:10       ` Laurent Pinchart
2026-07-02  8:16         ` David Hildenbrand (Arm)
2026-07-02 10:04       ` Lorenzo Stoakes
2026-07-02 11:51         ` David Hildenbrand (Arm)
2026-07-02 12:49           ` Lorenzo Stoakes
2026-07-02 13:41             ` Jani Nikula
2026-07-02 13:48               ` Jeff Layton
2026-07-02 13:26           ` Christian Brauner
2026-07-02 13:35             ` Christoph Hellwig
2026-07-02 13:47             ` Laurent Pinchart
2026-07-02 13:57             ` Lorenzo Stoakes
2026-07-02 14:09               ` Christian Brauner
2026-07-02 14:46                 ` Lorenzo Stoakes
2026-07-02 16:18                   ` Christian Brauner
2026-07-02 16:29                     ` Lorenzo Stoakes
2026-07-02  8:08     ` Laurent Pinchart
2026-07-02  8:28       ` Christian Brauner
2026-07-02 13:48         ` Carlos Maiolino
2026-07-02  9:24   ` Lorenzo Stoakes
2026-07-01 18:35 ` Jeff Layton
2026-07-01 18:53   ` Jakub Kicinski
2026-07-02  7:29     ` Christian Brauner
2026-07-02  7:28   ` Christian Brauner
2026-07-02  8:12 ` Jori Koolstra
2026-07-02  8:44   ` Vlastimil Babka (SUSE)
2026-07-02  9:09     ` Jori Koolstra
2026-07-02  9:39       ` Lorenzo Stoakes
2026-07-02  9:37     ` Lorenzo Stoakes
2026-07-02  9:38     ` Laurent Pinchart
2026-07-02  9:44       ` Lorenzo Stoakes
2026-07-02 11:57         ` Brian Foster
2026-07-02 12:18           ` Lorenzo Stoakes
2026-07-02 13:07             ` Laurent Pinchart
2026-07-02 13:37               ` Lorenzo Stoakes
2026-07-02 13:47                 ` Jori Koolstra
2026-07-02 13:09             ` Brian Foster
2026-07-02 13:25               ` Lorenzo Stoakes
2026-07-02 10:34     ` Krzysztof Kozlowski
2026-07-02 12:23       ` Lorenzo Stoakes
2026-07-02 12:39         ` Krzysztof Kozlowski
2026-07-02 12:53           ` Lorenzo Stoakes [this message]
2026-07-02 13:23       ` Laurent Pinchart
2026-07-02 10:27 ` Krzysztof Kozlowski
2026-07-02 11:27 ` Christoph Hellwig
2026-07-02 13:40   ` Carlos Maiolino

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=akZeZ9GTjSp1L58S@lucifer \
    --to=ljs@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=jkoolstra@xs4all.nl \
    --cc=jlayton@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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