From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com ([134.134.136.24]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fPt7W-00034s-7G for speck@linutronix.de; Mon, 04 Jun 2018 19:18:15 +0200 Subject: [MODERATED] Re: spectrev1+ References: <20180601171244.GA30216@char.us.oracle.com> <20180601212952.GA7354@char.us.oracle.com> <20180604153815.GU12198@hirez.programming.kicks-ass.net> <20180604163622.tpgwn64fz5oxwmh5@treble> <20180604165502.GV12217@hirez.programming.kicks-ass.net> <20180604171432.zqli236zeixen3yu@treble> From: Dave Hansen Message-ID: Date: Mon, 4 Jun 2018 10:18:09 -0700 MIME-Version: 1.0 In-Reply-To: <20180604171432.zqli236zeixen3yu@treble> Content-Type: multipart/mixed; boundary="WMXmmDFnbUvE9jURA5oK3X4u71SW9fEaj"; protected-headers="v1" To: speck@linutronix.de List-ID: This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156) --WMXmmDFnbUvE9jURA5oK3X4u71SW9fEaj Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 06/04/2018 10:14 AM, speck for Josh Poimboeuf wrote: > So is the general idea that we're going to insert 3,000 lfences??? Or > is there some reasonable way to weed out false positives? I think the original ~800 "hits" from Coverity ended up in something like 10 places that we had to mitigate, either with lfence or array_index_nospec(). They had to be culled down manually, though. --WMXmmDFnbUvE9jURA5oK3X4u71SW9fEaj--