On 01/03/17 at 01:15pm, Dave Jiang wrote:
>
>
> On 01/03/2017 11:24 AM, Dan Williams wrote:
> > On Tue, Jan 3, 2017 at 12:31 AM, Baoquan He wrote:
> >> Hi Dan,
> >>
> >> On 11/22/16 at 09:26am, Dan Williams wrote:
> >>> [ replying for Dave since he's offline today and tomorrow
On 01/03/17 at 01:15pm, Dave Jiang wrote:
>
>
> On 01/03/2017 11:24 AM, Dan Williams wrote:
> > On Tue, Jan 3, 2017 at 12:31 AM, Baoquan He wrote:
> >> Hi Dan,
> >>
> >> On 11/22/16 at 09:26am, Dan Williams wrote:
> >>> [ replying for Dave since he's offline today and tomorrow ]
> >>>
> >>> On
On 01/03/2017 11:24 AM, Dan Williams wrote:
> On Tue, Jan 3, 2017 at 12:31 AM, Baoquan He wrote:
>> Hi Dan,
>>
>> On 11/22/16 at 09:26am, Dan Williams wrote:
>>> [ replying for Dave since he's offline today and tomorrow ]
>>>
>>> On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar
On 01/03/2017 11:24 AM, Dan Williams wrote:
> On Tue, Jan 3, 2017 at 12:31 AM, Baoquan He wrote:
>> Hi Dan,
>>
>> On 11/22/16 at 09:26am, Dan Williams wrote:
>>> [ replying for Dave since he's offline today and tomorrow ]
>>>
>>> On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
*
On Tue, Jan 3, 2017 at 12:31 AM, Baoquan He wrote:
> Hi Dan,
>
> On 11/22/16 at 09:26am, Dan Williams wrote:
>> [ replying for Dave since he's offline today and tomorrow ]
>>
>> On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
>> >
>> > * Dave Jiang
On Tue, Jan 3, 2017 at 12:31 AM, Baoquan He wrote:
> Hi Dan,
>
> On 11/22/16 at 09:26am, Dan Williams wrote:
>> [ replying for Dave since he's offline today and tomorrow ]
>>
>> On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
>> >
>> > * Dave Jiang wrote:
>> >
>> >> CONFIG_RANDOMIZE_BASE
On Tue, Jan 03, 2017 at 04:31:37PM +0800, Baoquan He wrote:
> Hi Dan,
>
> On 11/22/16 at 09:26am, Dan Williams wrote:
> > [ replying for Dave since he's offline today and tomorrow ]
> >
> > On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
> > >
> > > * Dave Jiang
On Tue, Jan 03, 2017 at 04:31:37PM +0800, Baoquan He wrote:
> Hi Dan,
>
> On 11/22/16 at 09:26am, Dan Williams wrote:
> > [ replying for Dave since he's offline today and tomorrow ]
> >
> > On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
> > >
> > > * Dave Jiang wrote:
> > >
> > >>
Hi Dan,
On 11/22/16 at 09:26am, Dan Williams wrote:
> [ replying for Dave since he's offline today and tomorrow ]
>
> On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
> >
> > * Dave Jiang wrote:
> >
> >> CONFIG_RANDOMIZE_BASE relocates the kernel to
Hi Dan,
On 11/22/16 at 09:26am, Dan Williams wrote:
> [ replying for Dave since he's offline today and tomorrow ]
>
> On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
> >
> > * Dave Jiang wrote:
> >
> >> CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address.
> >> However it
On Wed, Nov 23, 2016 at 4:04 PM, Dave Chinner wrote:
> On Tue, Nov 22, 2016 at 11:01:32AM -0800, Dan Williams wrote:
>> On Tue, Nov 22, 2016 at 10:54 AM, Kees Cook wrote:
>> > On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams
>>
On Wed, Nov 23, 2016 at 4:04 PM, Dave Chinner wrote:
> On Tue, Nov 22, 2016 at 11:01:32AM -0800, Dan Williams wrote:
>> On Tue, Nov 22, 2016 at 10:54 AM, Kees Cook wrote:
>> > On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams
>> > wrote:
>> >> No, you're right, we need to handle multiple ranges.
On Tue, Nov 22, 2016 at 11:01:32AM -0800, Dan Williams wrote:
> On Tue, Nov 22, 2016 at 10:54 AM, Kees Cook wrote:
> > On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams
> > wrote:
> >> No, you're right, we need to handle multiple ranges. Since the
>
On Tue, Nov 22, 2016 at 11:01:32AM -0800, Dan Williams wrote:
> On Tue, Nov 22, 2016 at 10:54 AM, Kees Cook wrote:
> > On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams
> > wrote:
> >> No, you're right, we need to handle multiple ranges. Since the
> >> mem_avoid array is statically allocated
On Tue, Nov 22, 2016 at 11:01 AM, Dan Williams wrote:
> On Tue, Nov 22, 2016 at 10:54 AM, Kees Cook wrote:
>> On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams
>> wrote:
>>> [ replying for Dave since he's offline today and
On Tue, Nov 22, 2016 at 11:01 AM, Dan Williams wrote:
> On Tue, Nov 22, 2016 at 10:54 AM, Kees Cook wrote:
>> On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams
>> wrote:
>>> [ replying for Dave since he's offline today and tomorrow ]
>>>
>>> On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
On Tue, Nov 22, 2016 at 10:54 AM, Kees Cook wrote:
> On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams
> wrote:
>> [ replying for Dave since he's offline today and tomorrow ]
>>
>> On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar
On Tue, Nov 22, 2016 at 10:54 AM, Kees Cook wrote:
> On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams
> wrote:
>> [ replying for Dave since he's offline today and tomorrow ]
>>
>> On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
>>>
>>> * Dave Jiang wrote:
>>>
CONFIG_RANDOMIZE_BASE
On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams wrote:
> [ replying for Dave since he's offline today and tomorrow ]
>
> On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
>>
>> * Dave Jiang wrote:
>>
>>> CONFIG_RANDOMIZE_BASE
On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams wrote:
> [ replying for Dave since he's offline today and tomorrow ]
>
> On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
>>
>> * Dave Jiang wrote:
>>
>>> CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address.
>>> However it does
[ replying for Dave since he's offline today and tomorrow ]
On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
>
> * Dave Jiang wrote:
>
>> CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address.
>> However it does not take into account the
[ replying for Dave since he's offline today and tomorrow ]
On Tue, Nov 22, 2016 at 12:47 AM, Ingo Molnar wrote:
>
> * Dave Jiang wrote:
>
>> CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address.
>> However it does not take into account the memmap= parameter passed in from
>> the
* Dave Jiang wrote:
> CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address.
> However it does not take into account the memmap= parameter passed in from
> the kernel commandline.
memmap= parameters are often used as a list.
> [...] This results in the
* Dave Jiang wrote:
> CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address.
> However it does not take into account the memmap= parameter passed in from
> the kernel commandline.
memmap= parameters are often used as a list.
> [...] This results in the kernel sometimes being put
CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address.
However it does not take into account the memmap= parameter passed in from
the kernel commandline. This results in the kernel sometimes being put in
the middle of the user memmap. Check has been added in the kaslr in order
to
CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address.
However it does not take into account the memmap= parameter passed in from
the kernel commandline. This results in the kernel sometimes being put in
the middle of the user memmap. Check has been added in the kaslr in order
to
26 matches
Mail list logo