Re: [PATCH 0/2] Determine kernel text mapping size at runtime for x86_64

2016-12-09 Thread Baoquan He
On 12/08/16 at 02:00pm, Dave Anderson wrote: > > > - Original Message - > > On Wed, Dec 7, 2016 at 11:56 PM, Baoquan He wrote: > > > Dave Anderson ever told in Crash utility he makes judgement whether it's > > > a kaslr kernel by size of KERNEL_IMAGE_SIZE. As long as it's 1G, it's > > >

Re: [PATCH 0/2] Determine kernel text mapping size at runtime for x86_64

2016-12-08 Thread Dave Anderson
- Original Message - > On Wed, Dec 7, 2016 at 11:56 PM, Baoquan He wrote: > > Dave Anderson ever told in Crash utility he makes judgement whether it's > > a kaslr kernel by size of KERNEL_IMAGE_SIZE. As long as it's 1G, it's > > recognized as kaslr. Then the current upstream kernel has a

Re: [PATCH 0/2] Determine kernel text mapping size at runtime for x86_64

2016-12-08 Thread Kees Cook
On Wed, Dec 7, 2016 at 11:56 PM, Baoquan He wrote: > Dave Anderson ever told in Crash utility he makes judgement whether it's > a kaslr kernel by size of KERNEL_IMAGE_SIZE. As long as it's 1G, it's > recognized as kaslr. Then the current upstream kernel has a wrong behaviour, > it sets KERNEL_IMAG

[PATCH 0/2] Determine kernel text mapping size at runtime for x86_64

2016-12-07 Thread Baoquan He
Dave Anderson ever told in Crash utility he makes judgement whether it's a kaslr kernel by size of KERNEL_IMAGE_SIZE. As long as it's 1G, it's recognized as kaslr. Then the current upstream kernel has a wrong behaviour, it sets KERNEL_IMAGE_SIZE as 1G as long as CONFIG_RANDOMIZE_BASE is enabled, th