linux-kernel - Re: [PATCH] Documentation: Provide guidelines for kernel development tools

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] [day] [month] [year] [list]

Message-ID: <aQEAms7uBHLwiRJE@laps>
Date: Tue, 28 Oct 2025 13:42:50 -0400
From: Sasha Levin <sashal@...nel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>, linux-kernel@...r.kernel.org,
	Steven Rostedt <rostedt@...dmis.org>,
	Dan Williams <dan.j.williams@...el.com>,
	Theodore Ts'o <tytso@....edu>, Jonathan Corbet <corbet@....net>,
	Kees Cook <kees@...nel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Shuah Khan <shuah@...nel.org>
Subject: Re: [PATCH] Documentation: Provide guidelines for kernel development
 tools

On Tue, Oct 28, 2025 at 04:29:14PM +0100, Miguel Ojeda wrote:
>On Mon, Oct 27, 2025 at 9:13 PM Dave Hansen <dave.hansen@...ux.intel.com> wrote:
>> + - ChatGPT generated a new function in your patch to sort list entries.
>> + - A .c file in the patch was originally generated by Gemini but cleaned
>> +   up by hand.
>
>Like Jon, it also crossed my mind using just LLM here or perhaps
>mentioning "open" models. On the other hand, it is clear commercial
>models are getting used already, e.g. Gemini is in the commit log
>already and Claude is in the mailing list.

I *think* that this was based on the experience[1] Kees had with LLMs, and my
thoughts were that this example would match what a developer were to write if
they were asked to document the usage of tooling.

And yes, we shouldn't mention proprietary brand names in kernel docs, so I
fully agree with Jon and Miguel here. We should however encourage contributors
to list the actual tools/LLMs they used, as this could be interesting down the
road...


[1] https://hachyderm.io/@kees/114907228284590439

-- 
Thanks,
Sasha