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] [day] [month] [year] [list]

Message-ID: <20180218124649.lgaqfafskepsvup4@gmail.com>
Date:   Sun, 18 Feb 2018 13:46:49 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     "Raj, Ashok" <ashok.raj@...el.com>
Cc:     bp@...e.de, X86 ML <x86@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86/microcode/intel: Check microcode revision before
 updating sibling threads


* Raj, Ashok <ashok.raj@...el.com> wrote:

> 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.

Ok.

Thanks,

	Ingo