From: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
To: Chris Mason <clm@meta.com>
Cc: Theodore Tso <tytso@mit.edu>,
Roman Gushchin <roman.gushchin@linux.dev>,
Sean Christopherson <seanjc@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
SeongJae Park <sj@kernel.org>,
elkin@google.com, Christian Brauner <brauner@kernel.org>,
Dmitry Vyukov <dvyukov@google.com>,
Sasha Levin <sashal@kernel.org>,
Shakeel Butt <shakeel.butt@linux.dev>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Ian Rogers <irogers@google.com>,
Venkatesh Srinivas <venkateshs@chromium.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Introduce Sashiko (agentic review of Linux kernel changes)
Date: Fri, 3 Apr 2026 15:02:53 +0100 [thread overview]
Message-ID: <ac_HwYwkMF_tDcXS@lucifer> (raw)
In-Reply-To: <CAMpPgXXs6ojyyCd9hh8E8Q5cYZuKCfiozLgME4Jd8nAYpgwo2w@mail.gmail.com>
On Fri, Apr 03, 2026 at 08:34:26AM -0400, Chris Mason wrote:
> On Fri, Apr 3, 2026 at 8:23 AM Lorenzo Stoakes (Oracle) <ljs@kernel.org> wrote:
> >
> > On Fri, Apr 03, 2026 at 08:11:30AM -0400, Theodore Tso wrote:
> > > One other thing to consider is copyright. This issue is one we can
> > > safely ignore when we are asking LLM's to review code. But if ask
> > > LLM's to generate documentation, and then we cut and paste the
> > > generated text into kernel documentation, the copyright status of the
> > > generated text is not well defined.
> > >
> > > In Europe, the European Comission has promulgated that LLM output,
> > > having been generated by a machine, and not a human being, is not
> > > copyrighted. If a human being then makes changes, the combined work
> > > could be subject to copyright, and if it is merged into code that is
> > > subject to the GPL (for example), the combined work would also be
> > > subject to the original license. But that's only in Europe.
> > >
> > > But consider researchers were able to extract 96% of Harry Potter and
> > > the Sourcerer's Stone from Claude 3.7 Sonnet. So with the right
> > > prompt, if we get a paragraph that came from some published book about
> > > Linux, and it was dropped into the Documentation/ directory, that
> > > might be problematic, since even (or maybe especially) the European
> > > Union might want to take a hard line. (Do you hear the people sing,
> > > singing the songs of angry Victor Hugo's? :-)
> > >
> > > If we use an LLM model analyze docuemntation to identify gaps, and we
> > > take a bullet list of missing functions or semantics, and the human
> > > being writes new text from scratch, instead of cutting and pasting
> > > directly from LLM, that should be safe. But of course, I'm not a
> > > lawyer and I don't play one on TV.
> >
> > I don't think anybody's suggesting we use LLMs to generate documentation,
> > at least that's not how I interpreted it?
> >
> > I'm very much against that, it absolutely requires expert input, and I've
> > already personally rejected AI slop mm documentation submitted fairly
> > recently.
> >
>
> I agree we need to very closely review any LLM generated content, but
> the subsystem guides in the review prompts are mostly AI generated. I
> personally would enjoy them a lot more if they also contained harry
> potter exceprts, but we're not quite there yet.
Oh I wasn't aware of that! OK well then I take it back, Ted does have a point
(and emergent Harry Potter becomes a possibility ;)
>
> Ex: https://github.com/masoncl/review-prompts/blob/main/kernel/subsystem/mm-vma.md
BTW by linking that you are now nerdsniping me into wanting to modify that :)))
Not sure if intentional but if so... well played sir well played...
>
> I'm sure as these get reviewed we'll find bugs, inaccuracies, and the
> need to restructure, but it's not so widly wrong as to be useless
> either.
Yeah agreed!
>
> -chris
Cheers, Lorenzo
next prev parent reply other threads:[~2026-04-03 14:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 15:31 Introduce Sashiko (agentic review of Linux kernel changes) Roman Gushchin
2026-03-18 12:03 ` Lorenzo Stoakes (Oracle)
2026-03-18 18:33 ` Roman Gushchin
2026-03-18 18:50 ` Lorenzo Stoakes (Oracle)
2026-03-19 22:33 ` Roman Gushchin
2026-04-02 22:57 ` Sean Christopherson
2026-04-03 1:48 ` Roman Gushchin
2026-04-03 7:47 ` Lorenzo Stoakes (Oracle)
2026-04-03 12:11 ` Theodore Tso
2026-04-03 12:23 ` Lorenzo Stoakes (Oracle)
2026-04-03 12:34 ` Chris Mason
2026-04-03 14:02 ` Lorenzo Stoakes (Oracle) [this message]
2026-04-03 16:58 ` Chris Mason
2026-03-18 18:50 ` Chris Mason
2026-03-18 15:00 ` SeongJae Park
2026-03-18 18:43 ` Roman Gushchin
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=ac_HwYwkMF_tDcXS@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=clm@meta.com \
--cc=dvyukov@google.com \
--cc=elkin@google.com \
--cc=irogers@google.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lorenzo.stoakes@oracle.com \
--cc=pbonzini@redhat.com \
--cc=roman.gushchin@linux.dev \
--cc=sashal@kernel.org \
--cc=seanjc@google.com \
--cc=shakeel.butt@linux.dev \
--cc=sj@kernel.org \
--cc=tytso@mit.edu \
--cc=venkateshs@chromium.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