linux-kernel - Re: [PATCH 0/2] x86/microcode/intel: Extend BDW late-loading with platform id and LLC check

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:   Mon, 15 Jan 2018 10:59:43 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Jia Zhang <zhang.jia@...ux.alibaba.com>
Cc:     tony.luck@...el.com, mingo@...hat.com, hpa@...or.com,
        tglx@...utronix.de, x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] x86/microcode/intel: Extend BDW late-loading with
 platform id and LLC check

On Mon, Jan 15, 2018 at 01:43:21PM +0800, Jia Zhang wrote:
> The fix further reduces the impact for the BDW model which has to launch
> a machine reset in order to run microcode update in BIOS. This point is
> important for some vendors without the concern about machine reboot in
> order to fix up Spectre v2.

That's a ridiculous excuse - those vendors need to reboot to get these
fixes first. So what is the real reason?

Why can't they simply move to early loading like the rest of the world?

So srsly, how many times are we going to fix this erratum? Are you going
to come up with yet another fix *after* this one?

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.