xfs: do not take the iolock in xfs_inactive
authorChristoph Hellwig <hch@infradead.org>
Wed, 4 Jul 2012 15:13:31 +0000 (11:13 -0400)
committerBen Myers <bpm@sgi.com>
Sun, 29 Jul 2012 21:16:49 +0000 (16:16 -0500)
commit0b56185b0d64ef89dad1c85bb7403fa762cbe50d
treef46b40a37c5a27e4cf0ab9c99241350e679f9930
parentfe67be036ff2f713b1c5f24dd4cdffae75bcb97a
xfs: do not take the iolock in xfs_inactive

An inode that enters xfs_inactive has been removed from all global
lists but the inode hash, and can't be recycled in xfs_iget before
it has been marked reclaimable.  Thus taking the iolock in here
is not nessecary at all, and given the amount of lockdep false
positives it has triggered already I'd rather remove the locking.

The only change outside of xfs_inactive is relaxing an assert in
xfs_itruncate_extents.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Rich Johnston <rjohnston@sgi.com>
Signed-off-by: Ben Myers <bpm@sgi.com>
fs/xfs/xfs_inode.c
fs/xfs/xfs_vnodeops.c