From: Dave Chinner <david@fromorbit.com>
To: Alex Elder <aelder@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v3, 07/16] xfsprogs: metadump: use pointers in generate_obfuscated_name()
Date: Thu, 24 Feb 2011 12:47:12 +1100 [thread overview]
Message-ID: <20110224014712.GU3166@dastard> (raw)
In-Reply-To: <201102182121.p1ILL1AZ029097@stout.americas.sgi.com>
On Fri, Feb 18, 2011 at 03:21:01PM -0600, Alex Elder wrote:
> Switch from using array references to using pointers to refer to the
> pathname characters as they get generated. Also limit the scope of
> a few automatic variables.
>
> Signed-off-by: Alex Elder <aelder@sgi.com>
>
> The only update since the last post version is the addition of an
> ASSERT() in the loop generating the last 5 bytes.
One small comment below, otherwise:
Reviewed-by: Dave Chinner <dchinner@redhat.com>
> @@ -500,16 +502,17 @@ generate_obfuscated_name(
> */
> newhash = rol32(newhash, 3) ^ hash;
>
> + first = newp;
> high_bit = 0;
> - for (i = 5; i > 0; i--) {
> - int shift = (i - 1) * 7;
> -
> - newp[namelen - i] = ((newhash >> shift) & 0x7f) ^ high_bit;
> - if (is_invalid_char(newp[namelen - i])) {
> - newp[namelen - i] ^= 1;
> + for (shift = 28; shift >= 0; shift -= 7) {
> + *newp = (newhash >> shift & 0x7f) ^ high_bit;
I'd prefer not to have to refer to my C bible to remind myself what
the precedence of ">>" vs "&" is, so perhaps leaving the second set
of () in this statement would be a good idea.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-02-24 1:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 21:21 [PATCH v3, 07/16] xfsprogs: metadump: use pointers in generate_obfuscated_name() Alex Elder
2011-02-24 1:47 ` Dave Chinner [this message]
2011-02-25 18:13 ` [PATCH v4, " Alex Elder
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=20110224014712.GU3166@dastard \
--to=david@fromorbit.com \
--cc=aelder@sgi.com \
--cc=xfs@oss.sgi.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.