Sure, that works.
Le dim. 14 févr. 2016 03:45, Eric Snowberg a
écrit :
>
> > On Feb 13, 2016, at 9:08 AM, Eric Snowberg
> wrote:
> >
> >>
> >> On Feb 13, 2016, at 7:05 AM, Vladimir 'phcoder' Serbinenko <
> phco...@gmail.com> wrote:
> >>
> >>
> >>
> >> Le sam. 13 févr. 2016 01:51, Eric Snowberg
> On Feb 13, 2016, at 9:08 AM, Eric Snowberg wrote:
>
>>
>> On Feb 13, 2016, at 7:05 AM, Vladimir 'phcoder' Serbinenko
>> wrote:
>>
>>
>>
>> Le sam. 13 févr. 2016 01:51, Eric Snowberg a
>> écrit :
>> Prevent buffer over-read in grub_machine_mmap_iterate. This was
>> causing phys_base fro
> On Feb 13, 2016, at 7:05 AM, Vladimir 'phcoder' Serbinenko
> wrote:
>
>
>
> Le sam. 13 févr. 2016 01:51, Eric Snowberg a écrit
> :
> Prevent buffer over-read in grub_machine_mmap_iterate. This was
> causing phys_base from being calculated properly. This then
> caused the wrong value to be
Le sam. 13 févr. 2016 01:51, Eric Snowberg a
écrit :
> Prevent buffer over-read in grub_machine_mmap_iterate. This was
> causing phys_base from being calculated properly. This then
> caused the wrong value to be placed in ramdisk_image within
> struct linux_hdrs. Which prevented the ramdisk from
On powerpc-ieee1275 we use mmap_iterate to claim heap, so we can't malloc
here yet. But can we perhaps have at least 512 bytes fit more robustness?
Le sam. 13 févr. 2016 06:36, Andrei Borzenkov a
écrit :
> 13.02.2016 03:50, Eric Snowberg пишет:
> > Prevent buffer over-read in grub_machine_mmap_i
13.02.2016 03:50, Eric Snowberg пишет:
> Prevent buffer over-read in grub_machine_mmap_iterate. This was
> causing phys_base from being calculated properly. This then
> caused the wrong value to be placed in ramdisk_image within
> struct linux_hdrs. Which prevented the ramdisk from loading on
> boo
