All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: testing a loopback device without filesystem causes a crash
Date: Mon, 14 Sep 2009 17:36:40 +0200	[thread overview]
Message-ID: <20090914153640.GC25403@thorin> (raw)
In-Reply-To: <20090914084542.GK13423@riva.ucam.org>

On Mon, Sep 14, 2009 at 09:45:42AM +0100, Colin Watson wrote:
> On Sun, Sep 13, 2009 at 07:58:56PM +0100, ago wrote:
> > On fezie's request I am reporting a possible bug that I experienced
> > when running the following:
> > 
> > loopback loop0 /path/to/myfile
> > if [ -e (loop0)/some/file ]; then
> >  echo ok
> > fi
> > 
> > If /path/to/myfile does not contain a filesystem, grub2 crashes (there
> > is a sudden restart) when I run the test.
> 
> The following patch fixes this. OK to commit?
> 
> 2009-09-14  Colin Watson  <cjwatson@ubuntu.com>
> 
> 	* commands/test.c (get_fileinfo): Return immediately if
> 	grub_fs_probe fails.
> 
> Index: commands/test.c
> ===================================================================
> --- commands/test.c	(revision 2593)
> +++ commands/test.c	(working copy)
> @@ -88,6 +88,13 @@ test_parse (char **args, int *argn, int argc)
>        }
>  
>      fs = grub_fs_probe (dev);
> +    if (! fs)
> +      {
> +	grub_free (device_name);
> +	grub_device_close (dev);
> +	return;
> +      }
> +

Of course!

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      reply	other threads:[~2009-09-14 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-13 18:58 testing a loopback device without filesystem causes a crash ago
2009-09-14  8:45 ` Colin Watson
2009-09-14 15:36   ` Robert Millan [this message]

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=20090914153640.GC25403@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.