From: Willy Tarreau <w@1wt.eu>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: greg@kroah.com, edumazet@google.com,
Jonathan Corbet <corbet@lwn.net>,
skhan@linuxfoundation.org, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Documentation: explain how to find maintainers addresses for security reports
Date: Thu, 2 Apr 2026 21:05:45 +0200 [thread overview]
Message-ID: <ac6-CYmhwi87z_e7@1wt.eu> (raw)
In-Reply-To: <e9f0bbe9-fbff-45c8-af99-4c66982bd2cd@infradead.org>
On Thu, Apr 02, 2026 at 11:42:51AM -0700, Randy Dunlap wrote:
>
>
> 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.
If that's supposed to work, I'm indeed all for it! I must confess that
I have not even understood the reason for "../process" when coming from
the same directory, but I just picked that from existing entries.
Thanks for your feedback, much appreciated!
Willy
next prev parent reply other threads:[~2026-04-02 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 18:26 [PATCH 0/3] Documentation: clarify required info in security reports Willy Tarreau
2026-04-02 18:26 ` [PATCH 1/3] Documentation: minor updates to the security contacts Willy Tarreau
2026-04-02 18:26 ` [PATCH 2/3] Documentation: explain how to find maintainers addresses for security reports Willy Tarreau
2026-04-02 18:42 ` Randy Dunlap
2026-04-02 19:05 ` Willy Tarreau [this message]
2026-04-02 18:26 ` [PATCH 3/3] Documentation: clarify the mandatory and desirable info " Willy Tarreau
2026-04-02 18:50 ` Randy Dunlap
2026-04-02 19:03 ` Willy Tarreau
2026-04-02 19:17 ` Randy Dunlap
2026-04-02 19:20 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac6-CYmhwi87z_e7@1wt.eu \
--to=w@1wt.eu \
--cc=corbet@lwn.net \
--cc=edumazet@google.com \
--cc=greg@kroah.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.