Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751092AbeAPBGI (ORCPT + 1 other); Mon, 15 Jan 2018 20:06:08 -0500 Received: from mail-wr0-f175.google.com ([209.85.128.175]:35345 "EHLO mail-wr0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750740AbeAPBGH (ORCPT ); Mon, 15 Jan 2018 20:06:07 -0500 X-Google-Smtp-Source: ACJfBosR68QKd7Kzr6ONA23SZFUmD0IupBqkdD+XA6dZG3FQCRYdxok8vY7NhBvQBuqq9KRxz578YgWURIlBnN7FuX4= MIME-Version: 1.0 In-Reply-To: References: From: Akemi Yagi Date: Mon, 15 Jan 2018 17:05:45 -0800 X-Google-Sender-Auth: GjeuzF7uqWeFIgyUCdzN6d2TSHY Message-ID: Subject: Re: Reg : Spectre & Meltdown To: David Lang Cc: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Mon, Jan 15, 2018 at 4:50 PM, David Lang wrote: > the 4.4.112 patches that Greg just posted include a bunch of work for these > vulnerabilities. > > Who knows what has been backported to the kernel he is running. > k In RHEL (therefore CentOS), microcode comes from the microcode_ctl package which is currently at 2.1-22.2.el7. If you get the latest from Intel ( https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File ), that will update the microcode on your system to "date = 2017-11-20". As far as I can see, that changes the test result of 'Spectre Variant 2' from vuln to Not vuln. Akemi