xfs: push the ilock into xfs_zero_eof
authorChristoph Hellwig <hch@infradead.org>
Tue, 27 Mar 2012 14:34:49 +0000 (10:34 -0400)
committerBen Myers <bpm@sgi.com>
Mon, 14 May 2012 21:20:20 +0000 (16:20 -0500)
commit193aec10504e4c24521449c46317282141fb36e8
treeab68802be2bc151911732a78c3acd84604164b20
parentf38996f5768713fb60e1d2de66c097367d54bb6a
xfs: push the ilock into xfs_zero_eof

Instead of calling xfs_zero_eof with the ilock held only take it internally
for the minimall required critical section around xfs_bmapi_read.  This
also requires changing the calling convention for xfs_zero_last_block
slightly.  The actual zeroing operation is still serialized by the iolock,
which must be taken exclusively over the call to xfs_zero_eof.

We could in fact use a shared lock for the xfs_bmapi_read calls as long as
the extent list has been read in, but given that we already hold the iolock
exclusively there is little reason to micro optimize this further.

Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Mark Tinguely <tinguely@sgi.com>
Signed-off-by: Ben Myers <bpm@sgi.com>
fs/xfs/xfs_file.c
fs/xfs/xfs_iops.c