mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christian Brauner <brauner@kernel.org>,
	 tech-board-discuss@lists.linux.dev
Cc: linux-kernel@vger.kernel.org,
	ksummit-discuss@lists.linuxfoundation.org,
	christianvanbrauner@gmail.com
Subject: Re: LLM based rewrites
Date: Mon, 09 Mar 2026 09:16:04 -0700	[thread overview]
Message-ID: <f626dc4884b35cf1af0f2ab261ab672b73184bc4.camel@HansenPartnership.com> (raw)
In-Reply-To: <20260307-clean-room-6118793eb175@brauner>

On Sat, 2026-03-07 at 21:49 +0100, Christian Brauner wrote:
[...
> Fwiw, I was made aware that there's a tangentially related discussion
> on the distribution mailing list at [3].

The lawyers on the European Legal Network are already debating this
point.  However, I really doubt that feeding the code base into a LLM
and saying rewrite it will pass muster at least under the US legal
tests for originality: it's the same reason why you can't give an
engineering team the code base and say rewrite it.  You have to apply
the clean room principles of one team reducing the code base to an API
reference and a separate team reimplementing it as a new code base to
get the required separation from being a derived work.

My point not being the legal one, but the technical one that the clean
room reduction to an API and back to code can be done by independent
LLMs, but likely not on the scale that something as big as the kernel
would require.  So it could work for small code bases but would be
prohibitively costly for huge ones.

Regards,

James


      parent reply	other threads:[~2026-03-09 16:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 20:49 Christian Brauner
2026-03-09 13:57 ` Steven Rostedt
2026-03-09 15:31   ` H. Peter Anvin
2026-03-09 16:16     ` Steven Rostedt
2026-03-09 16:33       ` Jonathan Corbet
2026-03-09 16:55         ` H. Peter Anvin
2026-03-09 17:09           ` H. Peter Anvin
2026-03-09 18:19           ` James Bottomley
2026-03-09 18:34             ` Steven Rostedt
2026-03-09 18:38               ` Dr. David Alan Gilbert
2026-03-09 18:54               ` James Bottomley
2026-03-10  4:52           ` Theodore Tso
     [not found]             ` <CAMTJT3_cVaA7aJmDa6j288-qwP3jzvM_R2pdk+XmE+1U=Sovbg@mail.gmail.com>
2026-03-10 12:47               ` Theodore Tso
2026-03-10 14:10                 ` Dr. Greg
2026-03-09 16:05 ` Dave Hansen
2026-03-09 16:16 ` James Bottomley [this message]

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=f626dc4884b35cf1af0f2ab261ab672b73184bc4.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=brauner@kernel.org \
    --cc=christianvanbrauner@gmail.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tech-board-discuss@lists.linux.dev \
    /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

all inboxes | Powered by JetHome®