linux-kernel - Re: [PATCH] x86/microcode: 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]

Date:   Sat, 17 Feb 2018 11:42:48 -0200
From:   Henrique de Moraes Holschuh <hmh@....eng.br>
To:     Ashok Raj <ashok.raj@...el.com>
Cc:     bp@...e.de, X86 ML <x86@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/microcode: Check microcode revision before updating
 sibling threads

On Fri, 16 Feb 2018, Ashok Raj wrote:
> After updating microcode on one of the threads in the core, the
> thread sibling automatically gets the update since the microcode
> resources are shared. Check the ucode revision on the cpu before
> performing a ucode update.

I wonder when this broke, because it used to do that just fine.

I even had to explain to a couple Debian users that no, nothing was
broken and yes, while it looked like the kernel was skipping some
"CPUs", it was actually updating all of them...

-- 
  Henrique Holschuh