Re: [PATCH v5 03/21] x86, KASLR: Drop CONFIG_RANDOMIZE_BASE_MAX_OFFSET

* Kees Cook wrote: > > Also note the assertive tone: if this Kconfig feature is eanbled, we say > > that > > the kernel address _will_ be randomized, and we should make sure it is. (If > > for some weird reason randomization fails we should warn prominently during > > bootup.) > > This will

Re: [PATCH v5 03/21] x86, KASLR: Drop CONFIG_RANDOMIZE_BASE_MAX_OFFSET

On Fri, Apr 15, 2016 at 1:07 AM, Ingo Molnar wrote: > > * Kees Cook wrote: > >> From: Baoquan He >> >> Currently CONFIG_RANDOMIZE_BASE_MAX_OFFSET is used to limit the maximum >> offset for kernel randomization. This limit doesn't need to be a CONFIG >> since it is tied completely to KERNEL_IMAGE

Re: [PATCH v5 03/21] x86, KASLR: Drop CONFIG_RANDOMIZE_BASE_MAX_OFFSET

* Kees Cook wrote: > From: Baoquan He > > Currently CONFIG_RANDOMIZE_BASE_MAX_OFFSET is used to limit the maximum > offset for kernel randomization. This limit doesn't need to be a CONFIG > since it is tied completely to KERNEL_IMAGE_SIZE, and will make no sense > once physical and virtual off

[PATCH v5 03/21] x86, KASLR: Drop CONFIG_RANDOMIZE_BASE_MAX_OFFSET

From: Baoquan He Currently CONFIG_RANDOMIZE_BASE_MAX_OFFSET is used to limit the maximum offset for kernel randomization. This limit doesn't need to be a CONFIG since it is tied completely to KERNEL_IMAGE_SIZE, and will make no sense once physical and virtual offsets are randomized separately. Th