On Tue, Sep 9, 2014 at 12:49 PM, H. Peter Anvin wrote:
> setup_data is used by a variety of bootloaders. The first user was large
> memory machines with more than 128 memory areas.
>
> On September 9, 2014 12:45:00 PM PDT, Vivek Goyal wrote:
>>On Fri, Sep 05, 2014 at 10:32:56AM -0700, Kees
setup_data is used by a variety of bootloaders. The first user was large
memory machines with more than 128 memory areas.
On September 9, 2014 12:45:00 PM PDT, Vivek Goyal wrote:
>On Fri, Sep 05, 2014 at 10:32:56AM -0700, Kees Cook wrote:
>> On Fri, Sep 05, 2014 at 10:08:16PM +0800, Baoquan He
On Fri, Sep 05, 2014 at 10:32:56AM -0700, Kees Cook wrote:
> On Fri, Sep 05, 2014 at 10:08:16PM +0800, Baoquan He wrote:
> > From: Dave Young
> >
> > X86 will pass setup_data region while necessary, these regions could be
> > overwitten by kernel due to kaslr.
> >
> > Thus iterate and add setup
On Fri, Sep 05, 2014 at 10:32:56AM -0700, Kees Cook wrote:
On Fri, Sep 05, 2014 at 10:08:16PM +0800, Baoquan He wrote:
From: Dave Young dyo...@redhat.com
X86 will pass setup_data region while necessary, these regions could be
overwitten by kernel due to kaslr.
Thus iterate and add
setup_data is used by a variety of bootloaders. The first user was large
memory machines with more than 128 memory areas.
On September 9, 2014 12:45:00 PM PDT, Vivek Goyal vgo...@redhat.com wrote:
On Fri, Sep 05, 2014 at 10:32:56AM -0700, Kees Cook wrote:
On Fri, Sep 05, 2014 at 10:08:16PM
On Tue, Sep 9, 2014 at 12:49 PM, H. Peter Anvin h...@zytor.com wrote:
setup_data is used by a variety of bootloaders. The first user was large
memory machines with more than 128 memory areas.
On September 9, 2014 12:45:00 PM PDT, Vivek Goyal vgo...@redhat.com wrote:
On Fri, Sep 05, 2014 at
On 09/05/14 at 10:32am, Kees Cook wrote:
> On Fri, Sep 05, 2014 at 10:08:16PM +0800, Baoquan He wrote:
> > From: Dave Young
> >
> > X86 will pass setup_data region while necessary, these regions could be
> > overwitten by kernel due to kaslr.
> >
> > Thus iterate and add setup regions to
On Fri, Sep 05, 2014 at 10:08:16PM +0800, Baoquan He wrote:
> From: Dave Young
>
> X86 will pass setup_data region while necessary, these regions could be
> overwitten by kernel due to kaslr.
>
> Thus iterate and add setup regions to mem_avoid[] in this patch.
> Up to now there isn't a official
From: Dave Young
X86 will pass setup_data region while necessary, these regions could be
overwitten by kernel due to kaslr.
Thus iterate and add setup regions to mem_avoid[] in this patch.
Up to now there isn't a official data to state the maximal entries
setup data could use. So just set max
From: Dave Young dyo...@redhat.com
X86 will pass setup_data region while necessary, these regions could be
overwitten by kernel due to kaslr.
Thus iterate and add setup regions to mem_avoid[] in this patch.
Up to now there isn't a official data to state the maximal entries
setup data could use.
On Fri, Sep 05, 2014 at 10:08:16PM +0800, Baoquan He wrote:
From: Dave Young dyo...@redhat.com
X86 will pass setup_data region while necessary, these regions could be
overwitten by kernel due to kaslr.
Thus iterate and add setup regions to mem_avoid[] in this patch.
Up to now there isn't
On 09/05/14 at 10:32am, Kees Cook wrote:
On Fri, Sep 05, 2014 at 10:08:16PM +0800, Baoquan He wrote:
From: Dave Young dyo...@redhat.com
X86 will pass setup_data region while necessary, these regions could be
overwitten by kernel due to kaslr.
Thus iterate and add setup regions to
12 matches
Mail list logo
