From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 19 Feb 2019 12:12:59 -0000 Received: from mail.kernel.org ([198.145.29.99]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1gw4Gf-0002L2-KD for speck@linutronix.de; Tue, 19 Feb 2019 13:12:58 +0100 Date: Tue, 19 Feb 2019 13:12:48 +0100 From: Greg KH Subject: [MODERATED] Re: [PATCH v5 00/27] MDSv5 19 Message-ID: <20190219121248.GA23450@kroah.com> References: <20190213223332.GL4516@lindsey> <20190214165355.GM16922@tassilo.jf.intel.com> <20190214180021.GB11103@kroah.com> <20190214183359.GT16922@tassilo.jf.intel.com> <20190214185242.GB19664@kroah.com> <20190214195041.GX16922@tassilo.jf.intel.com> <20190215070613.GF14473@kroah.com> <20190215130601.GB16922@tassilo.jf.intel.com> MIME-Version: 1.0 In-Reply-To: <20190215130601.GB16922@tassilo.jf.intel.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Fri, Feb 15, 2019 at 05:06:01AM -0800, speck for Andi Kleen wrote: > > Slowing the whole kernel down for an ill-defined problem is not ok. You > > know that > > What do you mean by ill defined problem? > > Are you unclear on the group 4 vulnerabilities? I assume you've seen > the disclosures, or is that not correct? I have seen some things, but odds are I have not seen everything. Do you have a pointer to where I, and everyone else here, should be looking to read all of the relevant ones to make sure we actually are talking about the same thing? > Have you read Documentation/clearcpu.txt? Yes I did, and I responded to your patch with some simple questions about that file on Jan 22: Subject: Re: [PATCH v5 09/27] MDSv5 23 Message-ID: <20190122072652.GA7082@kroah.com> but never got a response from you :( Why I have to ask for a response again (which is what I did here) is odd... greg k-h