From: Barry Naujok <bnaujok@sgi.com>
To: xfs@oss.sgi.com
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/4] XFS: Case-insensitive support - ASCII only
Date: Tue, 13 May 2008 17:57:49 +1000 [thread overview]
Message-ID: <20080513075749.477238845@chook.melbourne.sgi.com> (raw)
This patch seems to resolve all issues I had with CI support with the
dentry cache.
My solution for negative dentries was to not call d_add() when the
inode was not found. I had to fix up the create so it would call
d_rehash if the entry was unhashed.
I've also applied the other previous suggestions and cleanups.
The only outstanding problem is case-preserving rename on a CI
filesystem. I will write a patch for passing flags down to the
fs-specific lookup once the nameidata patch mentioned by
Christoph has been removed.
--
next reply other threads:[~2008-05-13 8:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 7:57 Barry Naujok [this message]
2008-05-13 7:57 ` [PATCH 1/4] XFS: Name operation vector for hash and compare Barry Naujok
2008-05-13 8:31 ` Christoph Hellwig
2008-05-13 7:57 ` [PATCH 2/4] XFS: add op_flags field and helpers to xfs_da_args Barry Naujok
2008-05-13 8:34 ` Christoph Hellwig
2008-05-14 6:12 ` Barry Naujok
2008-05-13 7:57 ` [PATCH 3/4] XFS: Return case-insensitive match for dentry cache Barry Naujok
2008-05-13 8:57 ` Christoph Hellwig
2008-05-14 6:15 ` Barry Naujok
2008-05-14 7:55 ` Barry Naujok
2008-05-15 4:57 ` Christoph Hellwig
2008-05-15 5:14 ` Barry Naujok
2008-05-15 13:43 ` Anton Altaparmakov
2008-05-15 14:11 ` Christoph Hellwig
2008-05-16 0:30 ` Barry Naujok
2008-05-16 7:25 ` Anton Altaparmakov
2008-05-20 2:24 ` Barry Naujok
2008-05-20 18:23 ` Christoph Hellwig
2008-05-20 20:50 ` Sunil Mushran
2008-05-13 7:57 ` [PATCH 4/4] XFS: ASCII case-insensitive support Barry Naujok
2008-05-13 8:58 ` Christoph Hellwig
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=20080513075749.477238845@chook.melbourne.sgi.com \
--to=bnaujok@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--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