public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] PATCH: Fix for 4KB kernel corruption
Date: Fri, 16 Nov 2001 18:44:38 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805530@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805523@msgid-missing>

Hi Philippe,

You may or mayn't see this problem. It depends up on the EFI memory map. In
our case, it is so happening that bootmap is allocated from the end of one
of the reserved regions and corrupting that reserved region.

Thanks,
Suresh

> -----Original Message-----
> From: Philippe Gramoullé [mailto:philippe.gramoulle@mmania.com]
> Sent: Friday, November 16, 2001 2:24 AM
> To: Siddha, Suresh B
> Cc: linux-ia64@linuxia64.org
> Subject: Re: [Linux-ia64] PATCH: Fix for 4KB kernel corruption
> 
> 
> 
> Hi Siddha,
> 
> Can this corruption happen with on lion with 4Go of memory also ?
> 
> Thanks,
> 
> Philippe.
> 
> "Siddha, Suresh B" wrote:
> > 
> > Hi,
> > 
> > 4KB page size kernel is broken on Lion with 8GB memory. 
> ia64_boot_param
> > structure was getting corrupted. Appended patch fixes this problem.
> > 
> > PAGE_ALIGN is required because: rsvd_region[i].end need not 
> be page aligned
> > and in the next iteration of the for loop this can 
> potentially become
> > bootmap_start. This can lead to corruption of rsvd_region[i] as
> > init_bootmem() takes the pfn of bootmap_start and 
> initialises the bootmem.
> > 
> > Thanks,
> > Suresh
> > 
> > diff -u linux-2.4.14/arch/ia64/kernel/setup.c~
> > linux-2.4.14/arch/ia64/kernel/setup.c
> > --- linux-2.4.14/arch/ia64/kernel/setup.c~      Thu Nov 15 
> 16:27:23 2001
> > +++ linux-2.4.14/arch/ia64/kernel/setup.c       Thu Nov 15 
> 16:28:01 2001
> > @@ -175,7 +175,7 @@
> >                 /* nothing more available in this segment */
> >                 if (range_end == end) return 0;
> > 
> > -               free_start = rsvd_region[i].end;
> > +               free_start = PAGE_ALIGN(rsvd_region[i].end);
> >         }
> >         return 0;
> >  }
> > 
> > _______________________________________________
> > Linux-IA64 mailing list
> > Linux-IA64@linuxia64.org
> > http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 


  parent reply	other threads:[~2001-11-16 18:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16  2:05 [Linux-ia64] PATCH: Fix for 4KB kernel corruption Siddha, Suresh B
2001-11-16  2:05 ` Siddha, Suresh B
2001-11-16 10:24 ` Philippe Gramoullé
2001-11-16 18:44 ` Siddha, Suresh B [this message]
2001-11-19 21:40 ` David Mosberger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590698805530@msgid-missing \
    --to=suresh.b.siddha@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox