bug-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: initrd breaks if VMALLOC_RESERVE is increased - Linux


From: Yoshinori K. Okuji
Subject: Re: initrd breaks if VMALLOC_RESERVE is increased - Linux
Date: Sun, 11 Jan 2004 10:55:44 +0100
User-agent: KMail/1.5

On Saturday 10 January 2004 11:48, Timothy Baldwin wrote:
> Index: stage2/boot.c
> ===================================================================
> RCS file: /cvsroot/grub/grub/stage2/boot.c,v
> retrieving revision 1.44
> diff -u -r1.44 boot.c
> --- stage2/boot.c     18 Mar 2003 21:07:35 -0000      1.44
> +++ stage2/boot.c     9 Jan 2004 14:05:28 -0000
> @@ -332,10 +332,8 @@
>               switch (errnum)
>                 {
>                 case ERR_NUMBER_OVERFLOW:
> -                 /* If an overflow occurs, use the maximum address for
> -                    initrd instead. This is good, because MAXINT is
> -                    greater than LINUX_INITRD_MAX_ADDRESS.  */
> -                 linux_mem_size = LINUX_INITRD_MAX_ADDRESS;
> +                 /* If an overflow occurs, use MAXINT instead */
> +                 linux_mem_size = MAXINT;
>                   errnum = ERR_NONE;
>                   break;
>
> @@ -357,7 +355,7 @@
>
>                     /* Check an overflow.  */
>                     if (linux_mem_size > (MAXINT >> shift))
> -                     linux_mem_size = LINUX_INITRD_MAX_ADDRESS;
> +                     linux_mem_size = MAXINT;
>                     else
>                       linux_mem_size <<= shift;
>                   }

Why do you need these changes?

Okuji




reply via email to

[Prev in Thread] Current Thread [Next in Thread]