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: <6e9cab54-7b66-45e9-af96-e52b3eba1034@intel.com>
Date: Thu, 8 Jan 2026 11:10:40 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
 James Bottomley <James.Bottomley@...senpartnership.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 1/8/26 08:35, Lorenzo Stoakes wrote:
<snip>
>> +As with the output of any tooling,
>>
>> The result can be incorrect or inappropriate so
> 
> LGTM! :)
...

I tweaked James's version a wee bit, but I think I left the message in
place. How does this hunk look?

@@ -95,3 +95,8 @@ 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.
+
+Finally, always be prepared for tooling that produces incorrect or
+inappropriate content. Make sure you 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.