From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: r2558 made another use case for make_relative_to_its_root visible (else SEGFAULT)
Date: Sat, 05 Sep 2009 20:25:01 +0200 [thread overview]
Message-ID: <1252175101.6437.23.camel@fz.local> (raw)
In-Reply-To: <20090904192657.GA4059@thorin>
Am Freitag, den 04.09.2009, 21:26 +0200 schrieb Robert Millan:
> On Fri, Sep 04, 2009 at 08:52:44PM +0200, Felix Zielcke wrote:
> > r2558 actually enabled this code path which was (almost) never executed
> > before in probe():
> >
> > if (S_ISREG (st.st_mode))
> > {
> > /* Regular file. Verify that we can read it properly. */
> >
> > grub_file_t file;
> > grub_util_info ("reading %s via OS facilities", path);
> > filebuf_via_sys = grub_util_read_image (path);
> >
> > grub_util_info ("reading %s via GRUB facilities", path);
> > asprintf (&grub_path, "(%s)%s", drive_name, path);
> > file = grub_file_open (grub_path);
> > filebuf_via_grub = xmalloc (file->size);
> > grub_file_read (file, filebuf_via_grub, file->size);
> >
> > grub_util_info ("comparing");
> >
> > if (memcmp (filebuf_via_grub, filebuf_via_sys, file->size))
> > grub_util_error ("files differ");
> > }
> > printf ("%s\n", fs->name);
> >
> > If /boot is on a seperate partition and you run `grub-probe -t
> > fs /boot/grub/core.img' grub_file_open returns 0 because grub_path is
> > the full system path and not a relative path which GRUB needs.
>
> A proper fix for this would be too intrusive for 1.97. Unless someone
> has a bright idea, I'll comment it out untill we've released.
For the release this is probable the best idea.
--
Felix Zielcke
Proud Debian Maintainer
next prev parent reply other threads:[~2009-09-05 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 18:52 r2558 made another use case for make_relative_to_its_root visible (else SEGFAULT) Felix Zielcke
2009-09-04 19:26 ` Robert Millan
2009-09-05 18:25 ` Felix Zielcke [this message]
2009-09-05 20:04 ` Colin Watson
2009-09-05 20:37 ` Robert Millan
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=1252175101.6437.23.camel@fz.local \
--to=fzielcke@z-51.de \
--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.