linux-kernel - Re: AMD microcode loading broken on 32 bit

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: <52E81B90.8040604@oracle.com>
Date:	Tue, 28 Jan 2014 16:05:20 -0500
From:	Boris Ostrovsky <boris.ostrovsky@...cle.com>
To:	Borislav Petkov <bp@...en8.de>
CC:	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: AMD microcode loading broken on 32 bit

On 01/28/2014 03:52 PM, Borislav Petkov wrote:
> On Tue, Jan 28, 2014 at 03:43:57PM -0500, Boris Ostrovsky wrote:
>> It fixes the case when there is no microcode in initrd but when
>> microcode is corrupted (as was the case when we were pointing to Intel
>> binary) we still die. Neither container nor ucode_cpio.data is NULL in
>> this case.
> How is that possible? Did you generate a path in the cpio by the name of
>
> "kernel/x86/microcode/AuthenticAMD.bin"
>
> but with Intel microcode in it?
>

Yes. This was a bug in our build environment. It is fixed now but I put this
bug back when I was testing your patch.

-boris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/