From: Alex Elder <aelder@sgi.com>
To: xfs@oss.sgi.com
Subject: [PATCH, RFC 0/6] xfsprogs: fix generate_obfuscate_name()
Date: Wed, 06 Oct 2010 13:48:40 -0500 [thread overview]
Message-ID: <1286390920.1951.357.camel@doink> (raw)
I'm sending this out for the moment with an "RFC" tag
because I don't consider this work done (I want to do
some refinements, basically). But I wanted to get the
code out there for an initial review to see if there
are any major problems with what I'm proposing here.
This is fixing the problem in xfs_db metadump feature
in which the attempt to create an obfuscated filename
can result in an endless loop.
I've run it through all possible 6-character names
starting with 0x01 through 0x07 (and counting...)
and the new algorithm (which is basically contained
in patch 3 of the series) produces an alternate
path with the same hash as the original for all
cases. I also ran all the test cases I identified
previously and all compute an alternate path without
hanging.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2010-10-06 18:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1286390920.1951.357.camel@doink \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox