linux-kernel - Re: [PATCH] arch/x86/kernel/cpu/microcode/intel: don't store initrd's start

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, 25 Jul 2016 15:44:53 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Nicolai Stange <nicstange@...il.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arch/x86/kernel/cpu/microcode/intel: don't store
 initrd's start

On Mon, Jul 25, 2016 at 02:59:43PM +0200, Nicolai Stange wrote:
> Applied on top of next-20160722 and it boots

Does it apply the microcode too? Or your box doesn't need microcode?

> Doesn't this break the builtin-ucode case (!blobs.valid) where
> blobs.start is supposed to be zero?

Good point.

Well, it shouldn't because in the builtin case start should simply
contain the ASLR offset the physmem mapping was moved to and this offset
is exactly where the builtin images should be... Let me poke at it to
see whether I'm seeing things correctly.

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--