Hi Ingo, Kees, Baoquan and Chao
At 03/12/2018 06:57 PM, Ingo Molnar wrote:
[...]
So there's apparently a mis-design here:
- KASLR needs to be done very early on during bootup: - it's not realistic to
expect KASLR to be done with a booted up kernel, because pointers to various
KASLR-ed
On Mon, Mar 19, 2018 at 03:24:46PM +0800, Baoquan He wrote:
>On 03/12/18 at 08:04pm, Chao Fan wrote:
>> On Mon, Mar 12, 2018 at 11:57:27AM +0100, Ingo Molnar wrote:
>> >
>> >* Baoquan He wrote:
>> >
>> >> Hi Ingo,
>> >>
>> >> On 03/12/18 at 10:35am, Ingo Molnar wrote:
>> >> >
>> >> > * Chao Fan
On 03/12/18 at 08:04pm, Chao Fan wrote:
> On Mon, Mar 12, 2018 at 11:57:27AM +0100, Ingo Molnar wrote:
> >
> >* Baoquan He wrote:
> >
> >> Hi Ingo,
> >>
> >> On 03/12/18 at 10:35am, Ingo Molnar wrote:
> >> >
> >> > * Chao Fan wrote:
> >> >
> >> > > Long time no reply, rebase the patchset, chan
On 03/12/18 at 08:04pm, Chao Fan wrote:
> On Mon, Mar 12, 2018 at 11:57:27AM +0100, Ingo Molnar wrote:
> >> > > ***Background:
> >> > > People reported that kaslr may randomly chooses some positions
> >> > > which are located in movable memory regions. This will break memory
> >> > > hotplug featur
On Mon, Mar 12, 2018 at 11:57:27AM +0100, Ingo Molnar wrote:
>
>* Baoquan He wrote:
>
>> Hi Ingo,
>>
>> On 03/12/18 at 10:35am, Ingo Molnar wrote:
>> >
>> > * Chao Fan wrote:
>> >
>> > > Long time no reply, rebase the patchset, change the parameter name
>> > > from 'kaslr_mem' to 'kaslr_boot_m
* Baoquan He wrote:
> Hi Ingo,
>
> On 03/12/18 at 10:35am, Ingo Molnar wrote:
> >
> > * Chao Fan wrote:
> >
> > > Long time no reply, rebase the patchset, change the parameter name
> > > from 'kaslr_mem' to 'kaslr_boot_mem'. There's no more code change.
> > >
> > > ***Background:
> > > Peop
Hi Ingo,
On 03/12/18 at 10:35am, Ingo Molnar wrote:
>
> * Chao Fan wrote:
>
> > Long time no reply, rebase the patchset, change the parameter name
> > from 'kaslr_mem' to 'kaslr_boot_mem'. There's no more code change.
> >
> > ***Background:
> > People reported that kaslr may randomly chooses s
* Chao Fan wrote:
> Long time no reply, rebase the patchset, change the parameter name
> from 'kaslr_mem' to 'kaslr_boot_mem'. There's no more code change.
>
> ***Background:
> People reported that kaslr may randomly chooses some positions
> which are located in movable memory regions. This wil
8 matches
Mail list logo