linux-kernel - Re: 4.15.17 regression: bisected: timeout during microcode update

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: <20180418122212.GA4290@pd.tnic>
Date:   Wed, 18 Apr 2018 14:22:12 +0200
From:   Borislav Petkov <bp@...e.de>
To:     Vitezslav Samel <vitezslav@...el.cz>,
        Ashok Raj <ashok.raj@...el.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Subject: Re: 4.15.17 regression: bisected: timeout during microcode update

On Wed, Apr 18, 2018 at 02:08:40PM +0200, Vitezslav Samel wrote:
> I switched to firmware-in-kernel early loading and that works OK.

Ok, and keep using that from now on.

People should all move away from that late loading dance. I'm saying
that in case someone else reads this on lkml.

> But still, the reported issue is regression in 4.15.17 and 4.16+.

Oh, I know it is a regression.

@Ashok: anything particular about his microcode revision not being able
to stomach late loading?

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--