Re: [PATCH v3 1/7] x86, kaslr: Use init_size instead of run_size

From: Yinghai Lu
Date: Fri Mar 13 2015 - 22:47:19 EST

On Fri, Mar 13, 2015 at 5:27 AM, Ingo Molnar <mingo@xxxxxxxxxx> wrote:
> * Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
>> commit e6023367d779 ("x86, kaslr: Prevent .bss from overlaping initrd")
>> introduced one run_size for kaslr.
>> We should use real runtime size (include copy/decompress) aka init_size.
> Why, what happens if we don't change this?

While trying to update change log, found we still need to keep this run_size.
otherwise kaslr will find not needed big size of init_size instead of
max(output_len, run_size).

will refresh the patchset.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at