Re: [PATCH 2/3] Documentation: explain how to find maintainers addresses for security reports

Randy Dunlap
2026-04-02T18:42:53Z

On 4/2/26 11:26 AM, Willy Tarreau wrote:
> These days, 80% of the work done by the security team consists in
> locating the affected subsystem in a report, running get_maintainers on
> it, forwarding the report to these persons and responding to the reporter
> with them in Cc. This is a huge and unneeded overhead that we must try to
> lower for a better overall efficiency. This patch adds a complete section
> explaining how to figure the list of recipients to send the report to.
>
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: Greg KH <greg@kroah.com>
> Signed-off-by: Willy Tarreau <w@1wt.eu>
> ---
> Documentation/process/security-bugs.rst | 76 ++++++++++++++++++++++++-
> 1 file changed, 73 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/process/security-bugs.rst b/Documentation/process/security-bugs.rst
> index da7937fd59df..6937fa9fba5a 100644
> --- a/Documentation/process/security-bugs.rst
> +++ b/Documentation/process/security-bugs.rst

> Markdown, HTML and RST formatted reports are particularly frowned upon since
> they're quite hard to read for humans and encourage to use dedicated viewers,
> sometimes online, which by definition is not acceptable for a confidential
> -security report.
> +security report. Note that some mailers tend to mangle formatting of plain
> +text by default, please consult :doc:`the email client howto
> +<../process/email-clients>` for more info.

Just use the file name and let automarkup do its job:

text by default; please consult Documentation/process/email-clients.rst
for more information.

It's also more convenient for text readers that way.

>
> Disclosure and embargoed information
> ------------------------------------

--
~Randy