Date: Sat, 13 Apr 2013 20:06:49 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Yinghai Lu <yinghai@...nel.org> CC: Kees Cook <keescook@...omium.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, kernel-hardening@...ts.openwall.com, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, the arch/x86 maintainers <x86@...nel.org>, Jarkko Sakkinen <jarkko.sakkinen@...el.com>, Matthew Garrett <mjg@...hat.com>, Matt Fleming <matt.fleming@...el.com>, Eric Northup <digitaleric@...gle.com>, Dan Rosenberg <drosenberg@...curity.com>, Julien Tinnes <jln@...gle.com>, Will Drewry <wad@...omium.org> Subject: Re: [PATCH 6/6] x86: kaslr: relocate base offset at boot On 04/13/2013 05:37 PM, Yinghai Lu wrote: > > so decompress code position is changed? > > You may push out bss and other data area of run-time kernel of limit > that boot loader > chose according to setup_header.init_size. > aka that make those area overlap with ram hole or other area like > boot command line or initrd.... > Is there a strong reason to randomize the physical address on 64 bits (and if so, shouldn't we do it right?) -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.