All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] generic ELF loading
Date: Wed, 25 Oct 2006 07:53:23 +0200	[thread overview]
Message-ID: <200610250753.24339.okuji@enbug.org> (raw)
In-Reply-To: <1161720181.23331.25.camel@basalt.austin.ibm.com>

On Tuesday 24 October 2006 22:03, Hollis Blanchard wrote:
> Actually I'm not using the heap, I'm just directly copying wherever
> phdr->p_paddr says to. That's not a good thing actually; in the future
> we should add some error checking to make sure we don't clobber GRUB
> itself.

OK, then it's even worse. :(

You must not assume that GRUB can always load an OS image to an appropriate 
location directly. I know this is the case for the current implementation of  
the Multiboot loader, but it is a very bad idea, generally speaking.

What GRUB should do is first to load an image to somewhere then relocate it to 
the right place at boot time. On i386-pc, the OS area is used for this very 
purpose. The x86 Multiboot loader is just a mistake, and that's why we must 
rewrite it.

Okuji



  parent reply	other threads:[~2006-10-25  5:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13 22:37 [PATCH] generic ELF loading Hollis Blanchard
2006-10-13 22:40 ` [PATCH] ppc64 Linux ELF loader Hollis Blanchard
2006-10-14 15:33 ` [PATCH] generic ELF loading Yoshinori K. Okuji
2006-10-14 17:23   ` Tristan Gingold
2006-10-24 20:41     ` Hollis Blanchard
2006-10-24 20:03   ` Hollis Blanchard
2006-10-24 20:48     ` Johan Rydberg
2006-10-24 20:45       ` Hollis Blanchard
2006-10-25  5:53     ` Yoshinori K. Okuji [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-14  3:03 Mao, Bibo
2006-10-24 20:21 ` Hollis Blanchard

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=200610250753.24339.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.