Re: [PATCH v3 5/7] x86, kaslr: Consolidate mem_avoid array filling

2015-03-09 Thread Kees Cook
On Mon, Mar 9, 2015 at 6:10 PM, Yinghai Lu wrote: > On Mon, Mar 9, 2015 at 6:00 PM, Kees Cook wrote: >> On Sat, Mar 7, 2015 at 2:07 PM, Yinghai Lu wrote: >> >> This may be a stupid question, but are boot_params being used outside >> of the compressed loader? If so, it might make sense to split

Re: [PATCH v3 5/7] x86, kaslr: Consolidate mem_avoid array filling

2015-03-09 Thread Yinghai Lu
On Mon, Mar 9, 2015 at 6:00 PM, Kees Cook wrote: > On Sat, Mar 7, 2015 at 2:07 PM, Yinghai Lu wrote: > > This may be a stupid question, but are boot_params being used outside > of the compressed loader? If so, it might make sense to split that > change into a separate patch to go to stable, if

Re: [PATCH v3 5/7] x86, kaslr: Consolidate mem_avoid array filling

2015-03-09 Thread Kees Cook
On Sat, Mar 7, 2015 at 2:07 PM, Yinghai Lu wrote: > Now ZO sit end of the buffer, we can find out where is ZO text > and data/bss etc. > > [input, input+input_size) is copied compressed kernel, not the whole ZO. > [output, output+init_size) is the buffer for VO. > > [input+input_size,

Re: [PATCH v3 5/7] x86, kaslr: Consolidate mem_avoid array filling

2015-03-09 Thread Kees Cook
On Sat, Mar 7, 2015 at 2:07 PM, Yinghai Lu ying...@kernel.org wrote: Now ZO sit end of the buffer, we can find out where is ZO text and data/bss etc. [input, input+input_size) is copied compressed kernel, not the whole ZO. [output, output+init_size) is the buffer for VO. [input+input_size,

Re: [PATCH v3 5/7] x86, kaslr: Consolidate mem_avoid array filling

2015-03-09 Thread Yinghai Lu
On Mon, Mar 9, 2015 at 6:00 PM, Kees Cook keesc...@chromium.org wrote: On Sat, Mar 7, 2015 at 2:07 PM, Yinghai Lu ying...@kernel.org wrote: This may be a stupid question, but are boot_params being used outside of the compressed loader? If so, it might make sense to split that change into a

Re: [PATCH v3 5/7] x86, kaslr: Consolidate mem_avoid array filling

2015-03-09 Thread Kees Cook
On Mon, Mar 9, 2015 at 6:10 PM, Yinghai Lu ying...@kernel.org wrote: On Mon, Mar 9, 2015 at 6:00 PM, Kees Cook keesc...@chromium.org wrote: On Sat, Mar 7, 2015 at 2:07 PM, Yinghai Lu ying...@kernel.org wrote: This may be a stupid question, but are boot_params being used outside of the

[PATCH v3 5/7] x86, kaslr: Consolidate mem_avoid array filling

2015-03-07 Thread Yinghai Lu
Now ZO sit end of the buffer, we can find out where is ZO text and data/bss etc. [input, input+input_size) is copied compressed kernel, not the whole ZO. [output, output+init_size) is the buffer for VO. [input+input_size, output+init_size) is [_text, _end) for ZO. that could be first range in

[PATCH v3 5/7] x86, kaslr: Consolidate mem_avoid array filling

2015-03-07 Thread Yinghai Lu
Now ZO sit end of the buffer, we can find out where is ZO text and data/bss etc. [input, input+input_size) is copied compressed kernel, not the whole ZO. [output, output+init_size) is the buffer for VO. [input+input_size, output+init_size) is [_text, _end) for ZO. that could be first range in