Received: by 10.223.185.116 with SMTP id b49csp1012857wrg; Wed, 21 Feb 2018 10:33:27 -0800 (PST) X-Google-Smtp-Source: AH8x226LX4dRKIgIVvQUNBL+zpewY80fUWO2yxlUNvp6zxdgeIsazHXt0UNc86nlclAKeE9m9RKg X-Received: by 10.99.95.142 with SMTP id t136mr3375191pgb.94.1519238007697; Wed, 21 Feb 2018 10:33:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519238007; cv=none; d=google.com; s=arc-20160816; b=M21/kUoKv7lLim0UDs3h3MUKTOYiV/3ge3rhdc3fz4T+EfMQYNvEYG2/WRIfisTrpL mMeyVBXkCYGHPC69l9r89VkSg6hoixPBk8jFiEWNA04vGk0XFsTHwFMt3M/sBh2eNMoY XvtHH6hYkgrsp994PaaSOc8I0AYChtSOfKCAWYIid7v+lN1fVERk5zGGIjg5vFwVnwVw 0blgfylT0SKp96yI72uv25wo/az2hvDgIM35l5cHGdMtecKGJCug0rs31Vw6RKcmqr1c nGvj2Enfu+v94nMhCCXEHaK0ILvFbeclbpZpymz2mGXI707iDJM2e1KdzkIq/jISWUnw BlUA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=XsqeFS1hMDEVsZa5FgYd8SXjCPhwaEeE3CxjVJUb0Og=; b=z2b+DOhFWLwtNkC7H3RLTIbiRVevis+aePh3CAystifoAbX4fFGZF1oQIcpEwbuOF4 p1y16Q48pG0lKaxcsGk/QQA37hU/w9yrbXRRioxMLj7SVTT/Ume1fjkpwek8M6GYCrAj jmgXj2cbThuSDTp34Mi/eVWkufUNuyldiAw5m66zR/PbyLeVJGmeTaEvkaHiVMXBpays 0FHbwJ5hM7KderrdmxilHmh22tDz58HHvOTm2BQ6+kGpW60lD0rbSVjF9bG6Nw5rm1Yi EhZ2Y8kiyZSH3boBQn28znoEDAajBCj6yPIW6yWMLBQQF26MyFv4lTZFhCx8simDpYSK xTPg== 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 b127si1600059pgc.220.2018.02.21.10.33.09; Wed, 21 Feb 2018 10:33:27 -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 S965247AbeBUNHv (ORCPT + 99 others); Wed, 21 Feb 2018 08:07:51 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:41826 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965221AbeBUNHs (ORCPT ); Wed, 21 Feb 2018 08:07:48 -0500 Received: from localhost (LFbn-1-12258-90.w90-92.abo.wanadoo.fr [90.92.71.90]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id C0765FD5; Wed, 21 Feb 2018 13:07:47 +0000 (UTC) From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Arjan van de Ven , David Woodhouse , Andy Lutomirski , Arjan van de Ven , Borislav Petkov , Dan Williams , Dave Hansen , David Woodhouse , Josh Poimboeuf , Linus Torvalds , Peter Zijlstra , Thomas Gleixner , dave.hansen@intel.com, kvm@vger.kernel.org, pbonzini@redhat.com, Ingo Molnar Subject: [PATCH 4.15 049/163] x86/speculation: Correct Speculation Control microcode blacklist again Date: Wed, 21 Feb 2018 13:47:58 +0100 Message-Id: <20180221124533.139027524@linuxfoundation.org> X-Mailer: git-send-email 2.16.2 In-Reply-To: <20180221124529.931834518@linuxfoundation.org> References: <20180221124529.931834518@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.15-stable review patch. If anyone has any objections, please let me know. ------------------ From: David Woodhouse commit d37fc6d360a404b208547ba112e7dabb6533c7fc upstream. Arjan points out that the Intel document only clears the 0xc2 microcode on *some* parts with CPUID 506E3 (INTEL_FAM6_SKYLAKE_DESKTOP stepping 3). For the Skylake H/S platform it's OK but for Skylake E3 which has the same CPUID it isn't (yet) cleared. So removing it from the blacklist was premature. Put it back for now. Also, Arjan assures me that the 0x84 microcode for Kaby Lake which was featured in one of the early revisions of the Intel document was never released to the public, and won't be until/unless it is also validated as safe. So those can change to 0x80 which is what all *other* versions of the doc have identified. Once the retrospective testing of existing public microcodes is done, we should be back into a mode where new microcodes are only released in batches and we shouldn't even need to update the blacklist for those anyway, so this tweaking of the list isn't expected to be a thing which keeps happening. Requested-by: Arjan van de Ven Signed-off-by: David Woodhouse Cc: Andy Lutomirski Cc: Arjan van de Ven Cc: Borislav Petkov Cc: Dan Williams Cc: Dave Hansen Cc: David Woodhouse Cc: Greg Kroah-Hartman Cc: Josh Poimboeuf Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: arjan.van.de.ven@intel.com Cc: dave.hansen@intel.com Cc: kvm@vger.kernel.org Cc: pbonzini@redhat.com Link: http://lkml.kernel.org/r/1518449255-2182-1-git-send-email-dwmw@amazon.co.uk Signed-off-by: Ingo Molnar Signed-off-by: Greg Kroah-Hartman --- arch/x86/kernel/cpu/intel.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) --- a/arch/x86/kernel/cpu/intel.c +++ b/arch/x86/kernel/cpu/intel.c @@ -116,13 +116,14 @@ struct sku_microcode { u32 microcode; }; static const struct sku_microcode spectre_bad_microcodes[] = { - { INTEL_FAM6_KABYLAKE_DESKTOP, 0x0B, 0x84 }, - { INTEL_FAM6_KABYLAKE_DESKTOP, 0x0A, 0x84 }, - { INTEL_FAM6_KABYLAKE_DESKTOP, 0x09, 0x84 }, - { INTEL_FAM6_KABYLAKE_MOBILE, 0x0A, 0x84 }, - { INTEL_FAM6_KABYLAKE_MOBILE, 0x09, 0x84 }, + { INTEL_FAM6_KABYLAKE_DESKTOP, 0x0B, 0x80 }, + { INTEL_FAM6_KABYLAKE_DESKTOP, 0x0A, 0x80 }, + { INTEL_FAM6_KABYLAKE_DESKTOP, 0x09, 0x80 }, + { INTEL_FAM6_KABYLAKE_MOBILE, 0x0A, 0x80 }, + { INTEL_FAM6_KABYLAKE_MOBILE, 0x09, 0x80 }, { INTEL_FAM6_SKYLAKE_X, 0x03, 0x0100013e }, { INTEL_FAM6_SKYLAKE_X, 0x04, 0x0200003c }, + { INTEL_FAM6_SKYLAKE_DESKTOP, 0x03, 0xc2 }, { INTEL_FAM6_BROADWELL_CORE, 0x04, 0x28 }, { INTEL_FAM6_BROADWELL_GT3E, 0x01, 0x1b }, { INTEL_FAM6_BROADWELL_XEON_D, 0x02, 0x14 },