On 03/15/18 10:18, Kevin Wolf wrote:
Am 15.03.2018 um 17:55 hat Jack Schwartz geschrieben:
On 03/15/18 08:54, Kevin Wolf wrote:
Am 15.03.2018 um 06:19 hat Jack Schwartz geschrieben:
Hi Kevin.
My comments are inline...
On 2018-03-14 10:32, Kevin Wolf wrote:
The code path with a manually set
Am 15.03.2018 um 17:55 hat Jack Schwartz geschrieben:
> On 03/15/18 08:54, Kevin Wolf wrote:
> > Am 15.03.2018 um 06:19 hat Jack Schwartz geschrieben:
> > > Hi Kevin.
> > >
> > > My comments are inline...
> > >
> > > On 2018-03-14 10:32, Kevin Wolf wrote:
> > > > The code path with a manually set
On 03/15/18 08:54, Kevin Wolf wrote:
Am 15.03.2018 um 06:19 hat Jack Schwartz geschrieben:
Hi Kevin.
My comments are inline...
On 2018-03-14 10:32, Kevin Wolf wrote:
The code path with a manually set mh_load_addr in the Multiboot header
checks that load_end_addr <= load_addr, but the path whe
Am 15.03.2018 um 06:19 hat Jack Schwartz geschrieben:
> Hi Kevin.
>
> My comments are inline...
>
> On 2018-03-14 10:32, Kevin Wolf wrote:
> > The code path with a manually set mh_load_addr in the Multiboot header
> > checks that load_end_addr <= load_addr, but the path where load_end_addr
> > is
Hi Kevin.
My comments are inline...
On 2018-03-14 10:32, Kevin Wolf wrote:
The code path with a manually set mh_load_addr in the Multiboot header
checks that load_end_addr <= load_addr, but the path where load_end_addr
is automatically detected if 0 is given in the header misses the
correspondi
The code path with a manually set mh_load_addr in the Multiboot header
checks that load_end_addr <= load_addr, but the path where load_end_addr
is automatically detected if 0 is given in the header misses the
corresponding check. If the kernel binary size is larger than can fit in
the address space
