From: David Howells <dhowells@redhat.com>
To: viro@zeniv.linux.org.uk
Cc: Jan Harkes <jaharkes@cs.cmu.edu>, Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
codalist@coda.cs.cmu.edu, coda@cs.cmu.edu,
linux-ext4@vger.kernel.org, linux-afs@lists.infradead.org,
dhowells@redhat.com, linux-afs@lists.infradead.org,
linux-ext4@vger.kernel.org, linux-ntfs-dev@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] vfs: Make icache searchable under RCU [ver #2]
Date: Thu, 25 Apr 2019 16:01:36 +0100 [thread overview]
Message-ID: <155620449631.4720.8762546550728087460.stgit@warthog.procyon.org.uk> (raw)
Hi Al
Here are some patches that make the icache searchable under RCU. This
benefits ext4 (which can use it to find an inode to update the timestamps on)
and afs (which can use it to find a vnode to invalidate the callback promise
on).
It might also benefit NTFS, if its use ilookup5_nowait() can be substituted
for. I'm not sure whether it actually needs to wait for inodes that are
undergoing deletion.
The first patch in the series attempts to fix the non-use of locking in Coda
when it moves an inode between buckets because it needs to update the search
key.
Changes:
(v2)
Remove the old rehashing code from coda.
Use READ_ONCE() in ext4 to access i_state.
Minor fixes.
The patches can also be found on the following branch:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=icache-rcu
Thanks,
David
---
David Howells (6):
vfs, coda: Fix the lack of locking in FID replacement inode rehashing
vfs: Change inode_hash_lock to a seqlock
vfs: Allow searching of the icache under RCU conditions
afs: Use RCU inode cache search for callback resolution
ext4: Search for an inode to update under the RCU lock if we can
vfs: Delete find_inode_nowait()
fs/afs/callback.c | 12 ++
fs/coda/cnode.c | 16 ++-
fs/ext4/inode.c | 54 +++++----
fs/inode.c | 307 ++++++++++++++++++++++++++++++++++++----------------
include/linux/fs.h | 11 +-
5 files changed, 264 insertions(+), 136 deletions(-)
next reply other threads:[~2019-04-25 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 15:01 David Howells [this message]
2019-04-25 15:01 ` [PATCH 1/6] vfs, coda: Fix the lack of locking in FID replacement inode rehashing [ver #2] David Howells
2019-04-25 15:01 ` [PATCH 2/6] vfs: Change inode_hash_lock to a seqlock " David Howells
2019-04-25 15:02 ` [PATCH 3/6] vfs: Allow searching of the icache under RCU conditions " David Howells
2019-04-25 15:19 ` Al Viro
2019-04-25 15:45 ` David Howells
2019-04-25 15:02 ` [PATCH 4/6] afs: Use RCU inode cache search for callback resolution " David Howells
2019-04-25 15:02 ` [PATCH 5/6] ext4: Search for an inode to update under the RCU lock if we can " David Howells
2019-04-25 15:02 ` [PATCH 6/6] vfs: Delete find_inode_nowait() " David Howells
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=155620449631.4720.8762546550728087460.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=coda@cs.cmu.edu \
--cc=codalist@coda.cs.cmu.edu \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-afs@lists.infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=tytso@mit.edu \
--cc=viro@zeniv.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).