Re: [PATCH v6 04/11] x86/KASLR: Build identity mappings on demand

2016-05-06 Thread Kees Cook
On Fri, May 6, 2016 at 12:00 AM, Ingo Molnar wrote: > > * Kees Cook wrote: > >> From: Yinghai Lu >> >> Currently KASLR only supports relocation in a small physical range (from >> 16M to 1G), due to using the initial kernel page table identity mapping. >> To support ranges above this, we need to

Re: [PATCH v6 04/11] x86/KASLR: Build identity mappings on demand

2016-05-06 Thread Ingo Molnar
* Kees Cook wrote: > From: Yinghai Lu > > Currently KASLR only supports relocation in a small physical range (from > 16M to 1G), due to using the initial kernel page table identity mapping. > To support ranges above this, we need to have an identity mapping for the > desired memory range befor

[PATCH v6 04/11] x86/KASLR: Build identity mappings on demand

2016-05-05 Thread Kees Cook
From: Yinghai Lu Currently KASLR only supports relocation in a small physical range (from 16M to 1G), due to using the initial kernel page table identity mapping. To support ranges above this, we need to have an identity mapping for the desired memory range before we can decompress (and later run