From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] ELF program header
Date: Sun, 14 Oct 2007 14:00:55 +0200 [thread overview]
Message-ID: <20071014120055.GB16638@thorin> (raw)
In-Reply-To: <20071012220337.GB21996@coresystems.de>
On Sat, Oct 13, 2007 at 12:03:37AM +0200, Stefan Reinauer wrote:
> > /* FIXME: Should we support program headers at strange locations? */
> > if (ehdr->e_phoff + ehdr->e_phnum * ehdr->e_phentsize > MULTIBOOT_SEARCH)
> > return grub_error (GRUB_ERR_BAD_OS, "program header at a too high offset");
> >
> > This breaks self-boot in the LinuxBIOS target. Moving the Program header
> > (see attached patch) fixed it, with no apparent drawbacks or regressions in
> > any of the ELF loaders around (tested on LinuxBIOS ELF loader and Efika OF).
>
> I assume this was with LinuxBIOSv3 and Qemu?
Yes.
> We tried the same but the patch was a lot bigger, trying to actually
> leave space in the beginning. Your patch might be enough, that would be
> really nice.
That's the question. Do we really have to add more space, or is that space
already allocated for us?
> I didn't really get the sense behind the layers of grub
> magic around read() and write().
They're basicaly like pread() and pwrite() with the added functionality of a
verbose mode.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2007-10-14 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 16:19 [PATCH] ELF program header Robert Millan
2007-10-12 20:24 ` Andrei E. Warkentin
2007-10-14 11:57 ` Robert Millan
2007-10-12 22:03 ` Stefan Reinauer
2007-10-14 12:00 ` Robert Millan [this message]
2007-10-16 17:14 ` Marcin Kurek
2007-10-17 19:20 ` Stefan Reinauer
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=20071014120055.GB16638@thorin \
--to=rmh@aybabtu.com \
--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.