On Mon, Apr 15, 2013 at 3:42 PM, Kees Cook <keesc...@chromium.org> wrote: > On Mon, Apr 15, 2013 at 3:38 PM, Yinghai Lu <ying...@kernel.org> wrote: > >> so the decompressed image is not moved high? > > No, I mean the size of the relocated image is using z_extract_offset > as the end size of the relocated memory. See select_aslr_address. It > takes the chosen aslr offset plus the location of z_extract_offset and > keeps reducing the offset until it's inside the physical end of > memory.
My point is: If you move the decompressed high, for example, before aslr uncompressed vmlinx is on [1024g+16M, 1024g+256M). after aslr, it is on [1024g+16M + 32M, 1024g+256M + 32M). You will need to make sure that 32M is still RAM in e820 memmap. also those range should not be with boot_param, command line, and initrd. as bootloader could put boot_param, commandline and initrd in that 32M range. Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
