[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <155559635133.21702.4737487773869377967.stgit@warthog.procyon.org.uk>
Date: Thu, 18 Apr 2019 15:05:51 +0100
From: David Howells <dhowells@...hat.com>
To: viro@...iv.linux.org.uk
Cc: Jan Harkes <jaharkes@...cmu.edu>, Theodore Ts'o <tytso@....edu>,
Andreas Dilger <adilger.kernel@...ger.ca>,
codalist@...a.cs.cmu.edu, coda@...cmu.edu,
linux-ext4@...r.kernel.org, linux-afs@...ts.infradead.org,
dhowells@...hat.com, linux-afs@...ts.infradead.org,
linux-ext4@...r.kernel.org, linux-ntfs-dev@...ts.sourceforge.net,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [RFC PATCH 0/6] vfs: Make icache searchable under RCU
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.
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 | 11 ++
fs/ext4/inode.c | 41 ++++---
fs/inode.c | 309 ++++++++++++++++++++++++++++++++++++----------------
include/linux/fs.h | 11 +-
5 files changed, 260 insertions(+), 124 deletions(-)
Powered by blists - more mailing lists