diff options
author | Dave Chinner <dchinner@redhat.com> | 2011-03-22 22:23:39 +1100 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2011-03-24 21:16:32 -0400 |
commit | f283c86afe6aa70b733d1ecebad5d9464943b774 (patch) | |
tree | beaeca959996f2d8a00a997c56932dc5916bfec8 /fs/9p | |
parent | 02afc410f363f98ac4f186341e38dcec13fc0e60 (diff) | |
download | linux-f283c86afe6aa70b733d1ecebad5d9464943b774.tar.gz linux-f283c86afe6aa70b733d1ecebad5d9464943b774.tar.bz2 linux-f283c86afe6aa70b733d1ecebad5d9464943b774.zip |
fs: remove inode_lock from iput_final and prune_icache
Now that inode state changes are protected by the inode->i_lock and
the inode LRU manipulations by the inode_lru_lock, we can remove the
inode_lock from prune_icache and the initial part of iput_final().
instead of using the inode_lock to protect the inode during
iput_final, use the inode->i_lock instead. This protects the inode
against new references being taken while we change the inode state
to I_FREEING, as well as preventing prune_icache from grabbing the
inode while we are manipulating it. Hence we no longer need the
inode_lock in iput_final prior to setting I_FREEING on the inode.
For prune_icache, we no longer need the inode_lock to protect the
LRU list, and the inodes themselves are protected against freeing
races by the inode->i_lock. Hence we can lift the inode_lock from
prune_icache as well.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/9p')
0 files changed, 0 insertions, 0 deletions