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: <709fa6fd-95b0-45e1-aec6-bd7432662b20@lucifer.local>
Date: Thu, 8 Jan 2026 19:30:13 +0000
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Sasha Levin <sashal@...nel.org>, Dave Hansen <dave.hansen@...el.com>,
        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>, 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, Jan 08, 2026 at 07:28:13PM +0000, Lorenzo Stoakes wrote:
> On Thu, Jan 08, 2026 at 07:27:17PM +0100, Miguel Ojeda wrote:
> > On Thu, Jan 8, 2026 at 5:42 PM Sasha Levin <sashal@...nel.org> wrote:
> > >
> > > We already have something like this in Documentation/process/howto.rst:

Sorry I missed here that that you referenced another document.

I think it's useful to have the emphasis I mentioned in a single place so
people can be referred there as to our expectaitons re: tool-generated
code. People are far more likely to miss things if located elsewhere.

So if we have emphasis on this there, it should make it even more sensible
to have emphasis here too.

Thanks, Lorenzo