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 19:44:10 +0200
From:	Nicolai Stange <nicstange@...il.com>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Nicolai Stange <nicstange@...il.com>,
	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

Borislav Petkov <bp@...en8.de> writes:
> Yeah, we should tie this to CONFIG_RANDOMIZE_MEMORY. IOW, here's another
> version, I'll do some more hammering on it tomorrow.

Boots fine and updates microcode (as always, on top of next-20160722).


> It should take care of the builtin case too as there we have the
> microcode in the kernel text mapping which is already relocated when we
> go search for microcode blobs so no need for adjusting start then.

Now that you've got basically the same #ifdefery and if(->valid)'s in
your final result as I did, may I ask whether you would still consider
it as being simpler? In particular, what's the point of having that
->start if it's redundant and has to be corrected in a more or less
hackish way anyway?

Thanks,

Nicolai