linux-kernel - Re: [PATCH 0/6] randomize kernel physical address and virtual address separately

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, 02 Feb 2015 08:42:19 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Baoquan He <bhe@...hat.com>, linux-kernel@...r.kernel.org
CC:	tglx@...utronix.de, mingo@...hat.com, x86@...nel.org,
	keescook@...omium.org, vgoyal@...hat.com, whissi@...ssi.de
Subject: Re: [PATCH 0/6] randomize kernel physical address and virtual address
 separately

On 01/20/2015 07:37 PM, Baoquan He wrote:
>
> Leftover problem:
>      hpa want to see the physical randomization can cover the whole physical memory. I
> checked code and found it's hard to do. Because in arch/x86/boot/compressed/head_64.S
> an identity mapping of 4G is built and then kaslr and decompressing are done. The #PF
> handler solution which he suggested is only available after jump into decompressed
> kernel, namely in arch/x86/kernel/head_64.S. I didn't think of a way to do the whole
> memory covering for physical address randomization, any suggestion or idea?
>

Basically, it means adding an IDT and #PF handler to the decompression 
code.  Not really all that complex.

	-hpa


--
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/