All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	security@kernel.org, corbet@lwn.net, workflows@vger.kernel.org
Subject: Re: [PATCH 1/2] Documentation: security-bugs.rst: update preferences when dealing with the linux-distros group
Date: Mon, 3 Jul 2023 17:01:40 +0200	[thread overview]
Message-ID: <2023070320-nutty-elitism-0e6c@gregkh> (raw)
In-Reply-To: <2023070323-sloppy-panama-4868@gregkh>

On Mon, Jul 03, 2023 at 05:00:51PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Jun 30, 2023 at 11:14:05AM -0700, Kees Cook wrote:
> > On Fri, Jun 30, 2023 at 09:14:20AM +0200, Greg Kroah-Hartman wrote:
> > > Because the linux-distros group forces reporters to release information
> > > about reported bugs, and they impose arbitrary deadlines in having those
> > > bugs fixed despite not actually being kernel developers, the kernel
> > > security team recommends not interacting with them at all as this just
> > > causes confusion and the early-release of reported security problems.
> > > 
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > 
> > Yeah, this is good. It might make sense to explicitly detail the
> > rationale in security-bugs.rst (as you have in the commit log), but
> > perhaps that's too much detail.
> > 
> > Reviewed-by: Kees Cook <keescook@chromium.org>
> 
> Thanks for the review.  I'll keep this as-is as it's the content of the
> file that matters in the end.

Ok, that didn't come out well, let me try again.  Let's leave the text
as-is for now, thanks.

greg k-h

      reply	other threads:[~2023-07-03 15:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  7:14 [PATCH 1/2] Documentation: security-bugs.rst: update preferences when dealing with the linux-distros group Greg Kroah-Hartman
2023-06-30  7:14 ` [PATCH 2/2] Documentation: security-bugs.rst: clarify CVE handling Greg Kroah-Hartman
2023-06-30  7:21   ` Greg Kroah-Hartman
2023-06-30 18:18   ` Kees Cook
2023-07-02 12:39     ` Greg Kroah-Hartman
2023-07-03  4:08       ` Willy Tarreau
2023-07-03 15:00         ` Greg Kroah-Hartman
2023-07-03 18:35           ` Kees Cook
2023-07-03 19:05             ` Greg Kroah-Hartman
2023-07-03 19:26               ` Kees Cook
2023-07-03 19:35                 ` Willy Tarreau
2023-06-30 18:14 ` [PATCH 1/2] Documentation: security-bugs.rst: update preferences when dealing with the linux-distros group Kees Cook
2023-07-03 15:00   ` Greg Kroah-Hartman
2023-07-03 15:01     ` Greg Kroah-Hartman [this message]

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=2023070320-nutty-elitism-0e6c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@kernel.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.