From: Christoph Hellwig <hch@infradead.org>
To: Barry Naujok <bnaujok@sgi.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
viro@ftp.linux.org.uk
Subject: Re: RFC: case-insensitive rename support in the VFS
Date: Fri, 2 May 2008 02:22:52 -0400 [thread overview]
Message-ID: <20080502062252.GA4705@infradead.org> (raw)
In-Reply-To: <op.uaid26f13jf8g2@pc-bnaujok.melbourne.sgi.com>
On Fri, May 02, 2008 at 02:14:56PM +1000, Barry Naujok wrote:
> As some of you know, I've been working on CI support for XFS.
> Currently, the Linux VFS does not make this very easy and neat.
>
> One issue I've encountered is the case of rename in a CI
> filesystem where the destination is the same as the source
> (both parent and child) differing only in case.
>
> So, currently, do_rename() calls do_path_lookup() which
> gets the source and destination dentries, etc. The third
> parameter, flags, is stored in the nameidata structure
> which is passed to the filesystem implementations of
> lookup.
>
> vfs_rename() checks to see if the two dentry inodes are
> the same, and if so, just returns 0.
>
> I propose adding a 7th LOOKUP_xxx flag for the rename case
> where we indicate we are after an exact (non-CI) match for
> the destination name in the lookup call in do_rename.
>
> Filesystem support in lookup would check for this flag
> in addition to LOOKUP_CONTINUE not existing (ie. at the
> last component during lookup) and if so, do an exact
> lookup rather than a CI lookup as it normally would do.
> Traditional non-CI filesystems would ignore this flag.
I think passing a flag to the filesystem for this is fine, but
flag in nameidata won't do it since lookup is going to lose the
nameidata argument soon.
prev parent reply other threads:[~2008-05-02 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 4:14 RFC: case-insensitive rename support in the VFS Barry Naujok
2008-05-02 6:22 ` Christoph Hellwig [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=20080502062252.GA4705@infradead.org \
--to=hch@infradead.org \
--cc=bnaujok@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).