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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Jul 2016 16:27:55 +0200
From:	Nicolai Stange <nicstange@...il.com>
To:	Nicolai Stange <nicstange@...il.com>
Cc:	Borislav Petkov <bp@...en8.de>,
	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

Nicolai Stange <nicstange@...il.com> writes:
> Borislav Petkov <bp@...en8.de> writes:
>> 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.
>
> Hmm. From what I've seen, I've concluded that the builtin images'
> addresses are __va ones (assuming x86_64). I might be wrong though.

Clarification: "__va ones" that don't point into the physmem mapping but
somewhere else.