All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Marcel J.E. Mol" <marcel@mesa.nl>
Cc: George Dunlap <george.dunlap@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH] pygrub/GrubConf: fix boot problem for fedora 19 grub.cfg (2nd attempt)
Date: Wed, 26 Jun 2013 14:50:46 +0100	[thread overview]
Message-ID: <1372254646.7337.85.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20130624162132.GA16610@joshua.mesa.nl>

On Mon, 2013-06-24 at 18:21 +0200, Marcel J.E. Mol wrote:
> Booting a fedora 19 domU failed because a it could not properly
> parse the grub.cfg file. This was cased by
> 
> 	set default="${next_entry}"
> 

Any chance you could send us an example of the actual problematic
configuration file, ideally as a patch adding a new file to
tools/pygrub/examples/. That "test suite" is rather rudimentary (to the
extent I'm a bit embarrassed to call it a suite...) but collecting them
when a bug is fixed is a good way to grow it.

> This statement actually is within an 'if' statement, so maybe it would
> be better to skip code within if/fi blocks...
> But this patch seems to work fine.
> 
> Signed-off-by: Marcel Mol <marcel@mesa.nl>

This change looks good to me:
Acked-by: Ian Campbell <ian.campbell@citix.com>

George, WRT 4.3 what do you think? I think the change is low risk for
any grub.conf without "${next_entry}" in it and a clear improvement to
any which does.

> ---
>  tools/pygrub/src/GrubConf.py |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/tools/pygrub/src/GrubConf.py b/tools/pygrub/src/GrubConf.py
> index 629951f..6324c62 100644
> --- a/tools/pygrub/src/GrubConf.py
> +++ b/tools/pygrub/src/GrubConf.py
> @@ -427,6 +427,8 @@ class Grub2ConfigFile(_GrubConfigFile):
>                  if self.commands[com] is not None:
>                      if arg.strip() == "${saved_entry}":
>                          arg = "0"
> +                    elif arg.strip() == "${next_entry}":
> +                        arg = "0"
>                      setattr(self, self.commands[com], arg.strip())
>                  else:
>                      logging.info("Ignored directive %s" %(com,))
> -- 
> 1.7.7.6
> 

  reply	other threads:[~2013-06-26 13:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 16:21 [PATCH] pygrub/GrubConf: fix boot problem for fedora 19 grub.cfg (2nd attempt) Marcel J.E. Mol
2013-06-26 13:50 ` Ian Campbell [this message]
2013-06-26 18:14   ` Marcel J.E. Mol
2013-06-26 13:52 ` George Dunlap
2013-06-26 13:57   ` Wei Liu
2013-06-26 18:17   ` Marcel J.E. Mol
2013-06-26 15:01 ` Konrad Rzeszutek Wilk
2013-06-26 16:05   ` George Dunlap
2013-06-27 11:31     ` Ian Campbell
2014-04-04 15:15       ` Ian Jackson
2013-07-02 15:01 ` Konrad Rzeszutek Wilk
2013-07-02 23:07   ` Marcel J.E. Mol

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=1372254646.7337.85.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=marcel@mesa.nl \
    --cc=xen-devel@lists.xen.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.