All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Willy Tarreau <w@1wt.eu>
Cc: 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 0/3] Documentation: clarify required info in security reports
Date: Fri, 3 Apr 2026 13:11:47 +0200	[thread overview]
Message-ID: <2026040324-coping-vacation-7d64@gregkh> (raw)
In-Reply-To: <20260403062018.31080-1-w@1wt.eu>

On Fri, Apr 03, 2026 at 08:20:15AM +0200, Willy Tarreau wrote:
> Hi Greg,
> 
> I'm sending you the doc clarifications we discussed for the process of
> reporting security issues. It's cut into the 3 patches I shared this
> morning on the security list (plus two typos fixed and a paragraph
> asking for one single issue per report):
> 
>   - one patch that reminds our need for a valid e-mail address
>   - one that explains to reporters how to proceed to find maintainers
>     addresses, hoping we won't have to do it for 90% of reports anymore
>   - one that enumerates basic requirements for every report
> 
> I think it covers the difficulties we've faced this week. As always,
> we might possibly find tiny adjustments to add, but my goal would be
> for such updates to be merged in time to update the public page ASAP
> so that we can redirect incomplete reports in an attempt to lower the
> team's current load.

Looks great, thanks.  I've applied these to one of my trees and will get
them to Linus in time for 7.0-final.

greg k-h

  parent reply	other threads:[~2026-04-03 11:11 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
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 ` Greg KH [this message]
2026-04-03 11:51   ` [PATCH v2 0/3] Documentation: clarify required info in " 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=2026040324-coping-vacation-7d64@gregkh \
    --to=greg@kroah.com \
    --cc=corbet@lwn.net \
    --cc=edumazet@google.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 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.