Grub Development Archive on 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: [PATCH] Corrections to affs and sfs
Date: Sat, 7 Feb 2009 21:33:43 +0100	[thread overview]
Message-ID: <20090207203343.GG988@thorin> (raw)
In-Reply-To: <4963988E.1010304@wp.pl>

On Tue, Jan 06, 2009 at 06:44:46PM +0100, Krzysztof Smiechowicz wrote:
> Robert Millan pisze:
> 
> >>Index: fs/sfs.c
> >>===================================================================
> >>--- fs/sfs.c	(revision 1919)
> >>+++ fs/sfs.c	(working copy)
> >>@@ -172,7 +172,8 @@
> >> 	  return grub_errno;
> >> 	}
> >> 
> >>-      for (i = 0; i < grub_be_to_cpu16 (tree->nodes); i++)
> >>+      grub_uint16_t nodescount = grub_be_to_cpu16(tree->nodes);
> >>+      for (i = nodescount - 1; i >= 0; i--)
> >
> >nodescount is only used once; why adding a variable?
> >
> >> 	  /* Follow the tree down to the leaf level.  */
> >>-	  if ((grub_be_to_cpu32 (EXTNODE(tree, i)->key) >= block)
> >>+	  if ((grub_be_to_cpu32 (EXTNODE(tree, i)->key) <= block)
> >> 	      && !tree->leaf)
> >> 	    {
> >>-	      next = grub_be_to_cpu32 (EXTNODE (tree, i - 1)->data);
> >>-	      break;
> >>-	    }
> >>-
> >>-	  /* In case the last node is reached just use that one, it is
> >>-	     the right match.  */
> >>-	  if (i + 1 == grub_be_to_cpu16 (tree->nodes) && !tree->leaf)
> >>-	    {
> >> 	      next = grub_be_to_cpu32 (EXTNODE (tree, i)->data);
> >> 	      break;
> >> 	    }
> >
> >I'm not familiar with our SFS code.  Marco, if you have a minute could you
> >review this part?
> >
> 
> Hello,
> 
> Any news about applying this patch? :)

Since Marco (who wrote that file) is not currently active, and nobody else
seems to be able to test and/or proofread it, we could just trust that you
know what you're doing.

Please, could you resend the patch without the unneeded 'nodescount' and
a ChangeLog entry?

-- 
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-02-07 20:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22 19:55 [PATCH] Corrections to affs and sfs Krzysztof Smiechowicz
2008-11-28 20:14 ` Robert Millan
2008-11-29  8:27   ` Krzysztof Smiechowicz
2009-01-06 17:44   ` Krzysztof Smiechowicz
2009-02-07 20:33     ` Robert Millan [this message]
2009-02-11 19:39     ` Krzysztof Smiechowicz
  -- strict thread matches above, loose matches on Subject: below --
2009-02-22  1:30 Kalamatee
2009-02-27 19:51 ` 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=20090207203343.GG988@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox