linux-kernel - Re: [PATCH] [v3] Documentation: Provide guidelines for tool-generated content

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a60e0e566edbcbd70176045ae077176444ca25a9.camel@HansenPartnership.com>
Date: Thu, 08 Jan 2026 08:17:09 -0500
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, Dave Hansen
	 <dave.hansen@...el.com>
Cc: Dave Hansen <dave@...1.net>, Dave Hansen <dave.hansen@...ux.intel.com>, 
 linux-kernel@...r.kernel.org, Shuah Khan <shuah@...nel.org>, Kees Cook
 <kees@...nel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Miguel
 Ojeda <ojeda@...nel.org>, Luis Chamberlain <mcgrof@...nel.org>, SeongJae
 Park <sj@...nel.org>,  Dan Williams <dan.j.williams@...el.com>, Steven
 Rostedt <rostedt@...dmis.org>, NeilBrown <neilb@...mail.net>,  Theodore
 Ts'o <tytso@....edu>, Sasha Levin <sashal@...nel.org>, Jonathan Corbet
 <corbet@....net>,  Vlastimil Babka <vbabka@...e.cz>,
 workflows@...r.kernel.org, ksummit@...ts.linux.dev
Subject: Re: [PATCH] [v3] Documentation: Provide guidelines for
 tool-generated content

On Thu, 2026-01-08 at 11:56 +0000, Lorenzo Stoakes wrote:
> On Wed, Jan 07, 2026 at 04:20:04PM -0800, Dave Hansen wrote:
> > On 1/7/26 13:15, Lorenzo Stoakes wrote:
> > > Thinking LLMs are 'just another tool' is to say effectively that
> > > the kernel
> > > is immune from this. Which seems to me a silly position.
> > 
> > I had a good chat with Lorenzo on IRC. I had it in my head that he
> > wanted a really different document than the one I posted. After
> > talking,
> > it sounds like he had some much more modest changes in mind. I
> > caught
> > him at the end of his day, but I think he's planning to send out a
> > small
> > diff on top of what I posted so I can get a better idea of what he
> > wants
> > to see tweaked.
> 
> I enclose the suggested incremental change below.
> 
> Cheers, Lorenzo
> 
> ----8<----
> From ccefc4da6b929914c754c2f898b0eb17d7fb3ebd Mon Sep 17 00:00:00
> 2001
> From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
> Date: Thu, 8 Jan 2026 11:55:10 +0000
> Subject: [PATCH] suggestion
> 
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
> ---
>  Documentation/process/generated-content.rst | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/Documentation/process/generated-content.rst
> b/Documentation/process/generated-content.rst
> index 917d6e93c66d..1423ed9d971d 100644
> --- a/Documentation/process/generated-content.rst
> +++ b/Documentation/process/generated-content.rst
> @@ -95,3 +95,11 @@ choose how they handle the contribution. For
> example, they might:
>   - Ask the submitter to explain in more detail about the
> contribution
>     so that the maintainer can feel comfortable that the submitter
> fully
>     understands how the code works.
> +
> +If tools permit you to generate series entirely automatically,
> expect
> +additional scrutiny.
> +
> +As with the output of any tooling,


>  maintainers will not tolerate 'slop' -

Just delete this phrase (partly because it's very tied to a non-
standard and very recent use of the word slop, but mostly because it
doesn't add anything actionable to the reader).

> +you are expected to understand and to be able to defend everything
> you 
> +submit. If you are unable to do so, maintainers may choose to reject
> your
> +series outright.

And I thing the addition would apply to any tool used to generate a
patch set whether AI or not.

Regards,

James