public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: greg@kroah.com, edumazet@google.com, rdunlap@infradead.org,
	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 v2 2/3] Documentation: explain how to find maintainers addresses for security reports
Date: Fri, 3 Apr 2026 08:48:56 -0700	[thread overview]
Message-ID: <202604030845.9DBD539AB@keescook> (raw)
In-Reply-To: <20260403062018.31080-3-w@1wt.eu>

On Fri, Apr 03, 2026 at 08:20:17AM +0200, Willy Tarreau wrote:
> [...]
> +One difficulty for most first-time reporters is to figure the right list of
> +recipients to send a report to.  In the Linux kernel, all official maintainers
> +are trusted, so the consequences of accidentally including the wrong maintainer
> +are essentially a bit more noise for that person, i.e. nothing dramatic.  As

Yeah, this is the central point: we already trust maintainers; there is
nothing "special" about security@kernel.org.

> [...]
> +single line suitable for use in the To: field of a mailer like this::
> +
> +  $ ./scripts/get_maintainer.pl --no-tree --no-l --no-r --no-n --m \
> +    --no-git-fallback --no-substatus --no-rolestats --no-multiline \
> +    --pattern-depth 1 drivers/example.c
> +  dev1@example.com, dev2@example.org

To echo Greg, yeah, this is great, and has been an implicit action we've
done for years, so there's every reason to delegate it to the reporter
to avoid the round-trip.

Though I guess we'll see if these new instructions actually change
anything -- we still have people asking for CVE assignments. :P

Reviewed-by: Kees Cook <kees@kernel.org>

-- 
Kees Cook

  reply	other threads:[~2026-04-03 15:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03  6:20 [PATCH v2 0/3] Documentation: clarify required info in security reports Willy Tarreau
2026-04-03  6:20 ` [PATCH v2 1/3] Documentation: minor updates to the security contacts Willy Tarreau
2026-04-03  6:20 ` [PATCH v2 2/3] Documentation: explain how to find maintainers addresses for security reports Willy Tarreau
2026-04-03 15:48   ` Kees Cook [this message]
2026-04-03 16:39     ` Willy Tarreau
2026-04-03  6:20 ` [PATCH v2 3/3] Documentation: clarify the mandatory and desirable info " Willy Tarreau
2026-04-03 11:11 ` [PATCH v2 0/3] Documentation: clarify required info in " Greg KH
2026-04-03 11:51   ` 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=202604030845.9DBD539AB@keescook \
    --to=kees@kernel.org \
    --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=w@1wt.eu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox