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]
Date:   Fri, 4 Mar 2022 09:20:12 -0800
From:   Randy Dunlap <>
To:     Jonathan Corbet <>,
        Kees Cook <>,
        Thorsten Leemhuis <>
Cc:     Greg Kroah-Hartman <>,
        Stefano Zacchiroli <>,
        Steven Rostedt <>,
        Laura Abbott <>,
        Julia Lawall <>,
        Wenwen Wang <>,,,
Subject: Re: [PATCH] Documentation/process: Add Researcher Guidelines

On 3/4/22 09:16, Jonathan Corbet wrote:
> Kees Cook <> writes:
>> On Thu, Feb 24, 2022 at 09:19:24AM +0100, Thorsten Leemhuis wrote:
>>> Hmm, the intro for "Documentation/admin-guide/" states that "The
>>> following manuals are written for users of the kernel", but the added
>>> text afaics providing nothing regular users care about. So wouldn't it
>>> be better if this lived below Documentation/process/ ? It might not a
>>> really good fit either, but I'd say it's the better place.
>>> But well, the best person to know is Jonathan, who is listed as a
>>> Co-developer above, so maybe I'm wrong my suggestion is a bad one.
>> I started in process/ and eventually settled on admin-guide/ since that's
>> basically the "front page". But I agree, there isn't an obviously correct
>> place for it.
> Sorry, been a bit distracted...when we were working on this I was more
> focused on the text than the location.  My own feeling is that
> Documentation/process is a better place for this - that's where we tell
> the world how to work with the kernel community, after all.  I'm not
> going to dig in my heels and fight about it, but that's my sense.
> Otherwise, it kind of seems like this is ready to go in. I'd like to
> apply it before the merge window; lemme know where you want it in the
> end and we can get it done.

There is a v2 of this patch, but yes, it should be in process/ IMO also.


Powered by blists - more mailing lists