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>
Cc: phcoder@gmail.com
Subject: Re: [patch] deadloop in grub_ext2_iterate_dir
Date: Sun, 25 Oct 2009 01:37:33 +0200	[thread overview]
Message-ID: <20091024233733.GB18233@thorin> (raw)
In-Reply-To: <4AD9B5F0.40304@parallels.com>

On Sat, Oct 17, 2009 at 04:17:52PM +0400, Vasily Averin wrote:
> fix for deadloop in grub_ext2_iterate_dir:
> fpos is not updated if dirent.direntlen == 0

Committed, thanks.

On Sat, Oct 17, 2009 at 02:54:24PM +0200, Felix Zielcke wrote:
> For consistency we should either always use the grub_Xe_to_cpuYZ
> functions or never when checking for a 0 value.

I've set it to keep not using it.

-- 
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."



      parent reply	other threads:[~2009-10-24 23:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-17 12:17 [patch] deadloop in grub_ext2_iterate_dir Vasily Averin
2009-10-17 12:54 ` Felix Zielcke
2009-10-24 23:37 ` 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=20091024233733.GB18233@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.org \
    --cc=phcoder@gmail.com \
    /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.