Received: by 10.223.176.46 with SMTP id f43csp2333466wra; Thu, 25 Jan 2018 08:18:35 -0800 (PST) X-Google-Smtp-Source: AH8x2266QoZ8uI0e4kl1ivL2dLpHr/0UxJb30k0Vx/MUnnKg3oVdnH1I/JYvHv5cANhDa8InbaL8 X-Received: by 10.99.96.203 with SMTP id u194mr13596048pgb.167.1516897115803; Thu, 25 Jan 2018 08:18:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516897115; cv=none; d=google.com; s=arc-20160816; b=AdSbxj4ocBuLNlTkicSGOgkppFGKDvXvU1k1Dqh17YiK5GT5h3SakzQKhaFlEiylU0 qMpjGaOQPrLdf5YEmucJwi1/fIROg6vKeOwwlXFJgS4t5FTdWH2PYYin1WBuCBpGTPEC IEn6bwWnjJOcUh2UPrZSD0HK6lkpXjPcHS2YONNcWvdvSgowdeQRHUxJ7yWG1px8SkfM YRGHMnBdzAqEdsMBavLyHpaPNL1wsJer5IGwhzlXPM9dvwioFr8oUWed4eKpUXEqvkCl RSHA3VvCQvsJS++nhoTY3QX/zFmM8V2roM60Ji4EOVhIM1H8tKfiyQX/ORIYHf3tPMi3 b5kQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:arc-authentication-results; bh=vAfUJ0JnkheQTSRY4e0UMzgzq5Arh5MYZV5PcTQoFEY=; b=md2w5n5a6vi9NEYOeH+/CW77bTqYFt6k514xBsEDxw++RQq+OqjKNL1tvlPls7hF5Y vIxbgvuZzb9Ko/CVg8lcZobXrsHeyXFJkAMA2e5pLnBroezgHLQ87hiclB+GFFhkLtDU uwUy/sajd2MJcFC/M0q0zqE+v06ThS3M4IGUZk1o3f0+TOimeTZHbL0dVWQdfqz6ZHqx Z2Y6ZMMQtE5nApMS6ZiIzUKu4g++TT/JBelVY8XTIaY8q4uUXLbp8EBFkMCMTbGqdqrU +5/4jUvPxybDvF3hZAu3HFMrKeJ+An8BTLJumSSJnSnxir0V3d99/srNxI1MzSTsTU6x EeNQ== 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 w10si1723057pgc.656.2018.01.25.08.18.21; Thu, 25 Jan 2018 08:18:35 -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 S1751339AbeAYQRz (ORCPT + 99 others); Thu, 25 Jan 2018 11:17:55 -0500 Received: from www.llwyncelyn.cymru ([82.70.14.225]:40620 "EHLO fuzix.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751207AbeAYQRy (ORCPT ); Thu, 25 Jan 2018 11:17:54 -0500 Received: from alans-desktop (82-70-14-226.dsl.in-addr.zen.co.uk [82.70.14.226]) by fuzix.org (8.15.2/8.15.2) with ESMTP id w0PGGEh4030789; Thu, 25 Jan 2018 16:16:14 GMT Date: Thu, 25 Jan 2018 16:16:14 +0000 From: Alan Cox To: David Woodhouse Cc: Thomas Gleixner , arjan@linux.intel.com, karahmed@amazon.de, x86@kernel.org, linux-kernel@vger.kernel.org, tim.c.chen@linux.intel.com, bp@alien8.de, peterz@infradead.org, pbonzini@redhat.com, ak@linux.intel.com, torvalds@linux-foundation.org, gregkh@linux-foundation.org, dave.hansen@intel.com, ashok.raj@intel.com, mingo@kernel.org Subject: Re: [PATCH v4 6/7] x86/cpufeature: Blacklist SPEC_CTRL on early Spectre v2 microcodes Message-ID: <20180125161547.33e63bb3@alans-desktop> In-Reply-To: <1516887714.30244.121.camel@infradead.org> References: <1516872189-16577-1-git-send-email-dwmw@amazon.co.uk> <1516872189-16577-7-git-send-email-dwmw@amazon.co.uk> <1516876994.30244.51.camel@infradead.org> <1516879213.30244.74.camel@infradead.org> <1516887714.30244.121.camel@infradead.org> Organization: Intel Corporation X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Here's what I have now. I'm happy enough with this, so the main thing > I'm looking for is an ack from Alan for patch #5 of the series, if I've > got that sufficiently correct now. You have my ACK for patch 5: Any further changes I'll submit as updates once it's merged. I am happy with patch 5 and I think for 64bit we are probably done for the mainstream. VIA/Centaur data would be nice. The microcode otoh I don't think makes sense - do you want to be secure with a slightly higher risk of crashes or insecure ? Once you can point at a newer ucode for each case then yes I personally at least think it then makes sense to tell users they want the newer one. Alan