historical-speck.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: speck@linutronix.de
Subject: [MODERATED] Do we need this list anymore? (was Re: [PATCH] Raffle 0)
Date: Tue, 14 Jul 2020 13:00:11 +0200	[thread overview]
Message-ID: <20200714110011.GA1300507@kroah.com> (raw)
In-Reply-To: <676ec4fc-b0df-91a6-92af-46c6c51663ed@citrix.com>

On Tue, Jul 14, 2020 at 09:03:41AM +0100, speck for Andrew Cooper wrote:
> On 14/07/2020 06:57, speck for Greg KH wrote:
> > Also, why is this being sent to speck?  What is wrong with the normal
> > development process?
> 
> This has a CVE attached to it, and an embargo in November (both of which
> ought to be more clear in the email and/or commit message IMO).
> 
> Researchers have demonstrated a power analysis side-channel to recover
> keys from the AES-NI instructions, usable by unprivileged userspace
> given these world-usable perms.

Ok, that's something new, can we just tear down this list now and if we
need new lists, create them as we have documented in:
	https://www.kernel.org/doc/html/latest/process/embargoed-hardware-issues.html

That way, when we create a new list, we know what it is for, there's a
set time limit on it, and no one is confused like this patch caused.

We are already doing this for other issues happening, why shouldn't we
do it for this one as well?

thanks,

greg k-h

  parent reply	other threads:[~2020-07-14 11:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5f0cf7c5.1c69fb81.99805.3f5fSMTPIN_ADDED_BROKEN@mx.google.com>
2020-07-14  5:57 ` [MODERATED] Re: [PATCH] Raffle 0 Greg KH
2020-07-14  8:03   ` Andrew Cooper
2020-07-14  8:14     ` Greg KH
2020-07-14  8:20       ` Greg KH
2020-07-14  8:36         ` Andrew Cooper
2020-07-14  8:44           ` Greg KH
2020-07-14 11:00     ` Greg KH [this message]
2020-07-14 15:34       ` Do we need this list anymore? (was Re: [PATCH] Raffle 0) Thomas Gleixner
2020-07-14 22:47         ` [MODERATED] " Gomez Iglesias, Antonio
2020-07-15 13:16           ` Thomas Gleixner
2020-07-14  5:58 ` [MODERATED] Re: [PATCH] Raffle 0 Greg KH
2020-07-14  6:01 ` Greg KH
2020-07-14 22:39   ` Pawan Gupta

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=20200714110011.GA1300507@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=speck@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).