From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by galois.linutronix.de (Postfix) with ESMTPS id DE87940340 for ; Tue, 14 Jul 2020 13:00:14 +0200 (CEST) Date: Tue, 14 Jul 2020 13:00:11 +0200 From: Greg KH Subject: [MODERATED] Do we need this list anymore? (was Re: [PATCH] Raffle 0) Message-ID: <20200714110011.GA1300507@kroah.com> References: <5f0cf7c5.1c69fb81.99805.3f5fSMTPIN_ADDED_BROKEN@mx.google.com> <20200714055735.GB655193@kroah.com> <676ec4fc-b0df-91a6-92af-46c6c51663ed@citrix.com> MIME-Version: 1.0 In-Reply-To: <676ec4fc-b0df-91a6-92af-46c6c51663ed@citrix.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: 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