Re: [PATCH v3 4/7] x86, kaslr: Access the correct kaslr_enabled variable

2015-03-09 Thread Kees Cook
On Sat, Mar 7, 2015 at 2:07 PM, Yinghai Lu wrote: > Commit > > f47233c2d34f ("x86/mm/ASLR: Propagate base load address calculation") > > started passing KASLR status to kernel proper, but it uses a physical > address as the vaule, leading to parsing bogus KASLR status in kernel > proper. > >

Re: [PATCH v3 4/7] x86, kaslr: Access the correct kaslr_enabled variable

2015-03-09 Thread Kees Cook
On Sat, Mar 7, 2015 at 2:07 PM, Yinghai Lu ying...@kernel.org wrote: Commit f47233c2d34f (x86/mm/ASLR: Propagate base load address calculation) started passing KASLR status to kernel proper, but it uses a physical address as the vaule, leading to parsing bogus KASLR status in kernel

[PATCH v3 4/7] x86, kaslr: Access the correct kaslr_enabled variable

2015-03-07 Thread Yinghai Lu
Commit f47233c2d34f ("x86/mm/ASLR: Propagate base load address calculation") started passing KASLR status to kernel proper, but it uses a physical address as the vaule, leading to parsing bogus KASLR status in kernel proper. The setup_data linked list and thus the element which contains

[PATCH v3 4/7] x86, kaslr: Access the correct kaslr_enabled variable

2015-03-07 Thread Yinghai Lu
Commit f47233c2d34f (x86/mm/ASLR: Propagate base load address calculation) started passing KASLR status to kernel proper, but it uses a physical address as the vaule, leading to parsing bogus KASLR status in kernel proper. The setup_data linked list and thus the element which contains