Received: by 10.223.176.46 with SMTP id f43csp4644121wra; Tue, 23 Jan 2018 12:16:57 -0800 (PST) X-Google-Smtp-Source: AH8x2274R4G4m7gAdgefGe7hNqjdEMqw/XBsisR82k0oPqJdAwCK8mBM61lJvuqGZqXKlXBN2lVy X-Received: by 10.157.3.241 with SMTP id f104mr8705664otf.141.1516738617546; Tue, 23 Jan 2018 12:16:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516738617; cv=none; d=google.com; s=arc-20160816; b=uDkJIG7ftuAELaShcQrKxCCnwa9wpu+RoJoxB8hl5BOOeZDvTde8rFPDFI9rgB5/YW QL2Tn1pLPTqjCUosqip3ryrWYcVF6MTXcscs6lXJ+5gZMfduhKsf/cRLDVtFfxooa8FG VE0HRRgX+p4JzcQVEGeodJgMoyhgdW9fAXNc2ctHlhQvJabJ60Zy+ogvx58Zbd4AJhUg I4ZeoWoTHhGjiIZs5ux52G2OhFmbGMdTTZJU1pKV1kFje/Z6f0iEGYrsjg9osurCiJz+ wVSe5EKmY0XE33unEiT3L/MPso0N13t+u/09roC7/hmTv1hFSlIQHjaCd3Lo0sdn8eKb VrNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=kb2DwA4YWrJIWhup5rTewp+7wADPaD0lUsnMF79O9hY=; b=MO248Lg9pFw4orDQMdWtY+dr7zlJ3C+LzWRpT2yuQMtaw0zgK0C2A9RDrIVUlklD0/ IbQ62bhhHyxHdje4zSi4Jrsqmllx5YrmD3aqHMmxnsSss4Ai5t+sMjP06bKq4oN3t6Nl gnFpH3Xr4KlMDMxff1ueNHkR7wHYkJ6sscXtR9exHBpS8XIHhPs+XU9ZEHQ2PEH2y0on PVhsaBtIdP8A0ph6WIKU42DOKwGnVPDxgoJcUyPjNA6tySGzawt6UOEUExV+hYKJOyBN r0DajTjwUi9GLMpLDiRZzFRbRXHy9LqHY5jIdnv6NIMhwte6/cb46dVSfvWbdJ4ElOjQ KSDQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a2si9095345itg.59.2018.01.23.12.16.44; Tue, 23 Jan 2018 12:16:57 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752549AbeAWUQU (ORCPT + 99 others); Tue, 23 Jan 2018 15:16:20 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:56021 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752340AbeAWUQS (ORCPT ); Tue, 23 Jan 2018 15:16:18 -0500 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id 012CB8014F; Tue, 23 Jan 2018 21:16:15 +0100 (CET) Date: Tue, 23 Jan 2018 21:16:15 +0100 From: Pavel Machek To: David Woodhouse Cc: Linus Torvalds , KarimAllah Ahmed , Linux Kernel Mailing List , Andi Kleen , Andrea Arcangeli , Andy Lutomirski , Arjan van de Ven , Ashok Raj , Asit Mallick , Borislav Petkov , Dan Williams , Dave Hansen , Greg Kroah-Hartman , "H . Peter Anvin" , Ingo Molnar , Janakarajan Natarajan , Joerg Roedel , Jun Nakajima , Laura Abbott , Masami Hiramatsu , Paolo Bonzini , Peter Zijlstra , Radim =?utf-8?B?S3LEjW3DocWZ?= , Thomas Gleixner , Tim Chen , Tom Lendacky , kvm@vger.kernel.org, x86@kernel.org, Arjan Van De Ven Subject: Re: [RFC 09/10] x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation Message-ID: <20180123201615.GA6957@amd> References: <1516476182-5153-1-git-send-email-karahmed@amazon.de> <1516476182-5153-10-git-send-email-karahmed@amazon.de> <1516566497.9814.78.camel@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1516566497.9814.78.camel@infradead.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun 2018-01-21 20:28:17, David Woodhouse wrote: > On Sun, 2018-01-21 at 11:34 -0800, Linus Torvalds wrote: > > All of this is pure garbage. > > > > Is Intel really planning on making this shit architectural? Has > > anybody talked to them and told them they are f*cking insane? > > > > Please, any Intel engineers here - talk to your managers.  > > If the alternative was a two-decade product recall and giving everyone > free CPUs, I'm not sure it was entirely insane. > > Certainly it's a nasty hack, but hey — the world was on fire and in the > end we didn't have to just turn the datacentres off and go back to goat > farming, so it's not all bad. Well, someone at Intel put world on fire. And then was selling faulty CPUs for half a year while world was on fire; they knew they are faulty yet they sold them anyway. Then Intel talks about how great they are and how security is important for them.... Intentionaly confusing between Meltdown and Spectre so they can mask how badly they screwed. And without apologies. > As a hack for existing CPUs, it's just about tolerable — as long as it > can die entirely by the next generation. > > So the part is I think is odd is the IBRS_ALL feature, where a future > CPU will advertise "I am able to be not broken" and then you have to > set the IBRS bit once at boot time to *ask* it not to be broken. That > part is weird, because it ought to have been treated like the RDCL_NO > bit — just "you don't have to worry any more, it got better". And now Intel wants to cheat at benchmarks, to put companies that do right thing at disadvantage and thinks that that's okay because world was on fire? At this point, I believe that yes, product recall would be appropriate. If Intel is not willing to do it on their own, well, perhaps courts can force them. Ouch and I wound not mind some jail time for whoever is responsible for selling known-faulty CPUs to the public. Oh, and still no word about the real fixes. World is not only Linux, you see? https://pavelmachek.livejournal.com/140949.html?nojs=1 Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html