linux-kernel - Re: [PATCH] x86/microcode/intel: Check microcode revision before updating sibling threads

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180217121042.GA23981@araj-mobl1.jf.intel.com>
Date:   Sat, 17 Feb 2018 04:10:43 -0800
From:   "Raj, Ashok" <ashok.raj@...el.com>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     bp@...e.de, X86 ML <x86@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ashok Raj <ashok.raj@...el.com>
Subject: Re: [PATCH] x86/microcode/intel: Check microcode revision before
 updating sibling threads

Hi Ingo

On Sat, Feb 17, 2018 at 08:50:53AM +0100, Ingo Molnar wrote:
> 
> Also, more fundamentally, during microcode early testing, isn't it possible for 
> internal iterations of the microcode to have the same revision, but be different?

Atleast we don't do that here. Such debug microcode isn't OS loadable. 
Anything that comes out ready for OS loading, the version will keep moving.

> This patch would prevent re-loading it - for a seemingly minimal benefit.

Cheers,
Ashok