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: <20180418120839.GA5655@pc11.op.pod.cz>
Date:   Wed, 18 Apr 2018 14:08:40 +0200
From:   Vitezslav Samel <vitezslav@...el.cz>
To:     Borislav Petkov <bp@...e.de>
Cc:     Ashok Raj <ashok.raj@...el.com>,
        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 12:07:21PM +0200, Borislav Petkov wrote:
> On Wed, Apr 18, 2018 at 10:11:40AM +0200, Vitezslav Samel wrote:
> >   Could be done anything to prevent this panic?
> 
> Yes, for starters, is there anything preventing you from using an initrd
> and doing early microcode loading?
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/x86/microcode.txt
> 
> If no, consider doing that and not using the late method which is
> problematic at best.

  I switched to firmware-in-kernel early loading and that works OK.
But still, the reported issue is regression in 4.15.17 and 4.16+.

	Thanks,

		Vita