All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Steven Rostedt <rostedt@goodmis.org>, "H. Peter Anvin" <hpa@zytor.com>
Cc: Christian Brauner <brauner@kernel.org>,
	tech-board-discuss@lists.linux.dev, linux-kernel@vger.kernel.org,
	ksummit-discuss@lists.linuxfoundation.org,
	christianvanbrauner@gmail.com
Subject: Re: LLM based rewrites
Date: Mon, 09 Mar 2026 10:33:12 -0600	[thread overview]
Message-ID: <871phtvu7r.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260309121629.21cabc25@gandalf.local.home>

Steven Rostedt <rostedt@goodmis.org> writes:

> On Mon, 09 Mar 2026 08:31:03 -0700
> "H. Peter Anvin" <hpa@zytor.com> wrote:
>
>> It is somewhat hard to see how that would constitute a "clean-room"
>> rewrite. A clean-room rewrite entails two teams, one (the "clean" room)
>> which must be certified to have never seen the code in question, and all
>> communications between the two teams must be auditable.
>
> I was thinking the same.

The argumentation that is being made (which I am trying to reproduce but
am *not* advocating) is that "a clean-room rewrite is just one means to
an end" and that, in this specific case, the code being rewritten was
explicitly excluded from the context given to the bot (though that turns
out not to entirely be the case).  In theory, it only had the desired
API and a set of tests available to it.

The fact that every version of chardet was surely in its training data
is not deemed to be relevant.

jon

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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 20:49 LLM based rewrites 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 [this message]
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

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=871phtvu7r.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=brauner@kernel.org \
    --cc=christianvanbrauner@gmail.com \
    --cc=hpa@zytor.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.