From: Christoph Hellwig <hch@infradead.org>
To: Alex Elder <aelder@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 01/12] xfsprogs: some things aren't all that special
Date: Mon, 10 Jan 2011 15:11:38 -0500 [thread overview]
Message-ID: <20110110201137.GA27277@infradead.org> (raw)
In-Reply-To: <1293741599.2294.342.camel@doink>
On Thu, Dec 30, 2010 at 02:39:59PM -0600, Alex Elder wrote:
> Move the check for short file names out of is_special_dirent() and
> into generate_obfuscated_name(). That way the check is more
> directly associated with the algorithm that requires it.
>
> Similarly, move the check for inode == 0, since that case has to do
> with storing extended attributes (not files) in the name table.
>
> As a result, is_special_dirent() is really only focused on whether a
> given file is in the lost+found directory.
>
> Rename is_special_dirent() to reflect its more specific purpose.
>
> And use a cast to elminate a compile warning in calls to
> libxfs_da_hashname().
I think Dave's resync of libxfs takes care of that bit. Either way it
really should be a separate patch.
Also you've stopped overwriting orphanage_ino if it already exists.
I don't think this really matters as we won't have two inodes with the
same name below the root inode. Either way it should be documented in
the changelog.
Otherwise the change looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-10 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 20:39 [PATCH 01/12] xfsprogs: some things aren't all that special Alex Elder
2011-01-10 20:11 ` Christoph Hellwig [this message]
2011-01-10 20:22 ` 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=20110110201137.GA27277@infradead.org \
--to=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox