xfs: xfs_ifree doesn't need to modify the inode buffer
authorDave Chinner <dchinner@redhat.com>
Thu, 27 Jun 2013 06:04:50 +0000 (16:04 +1000)
committerBen Myers <bpm@sgi.com>
Thu, 27 Jun 2013 18:31:04 +0000 (13:31 -0500)
commit1baaed8fa955ab0d23aab24477dae566ed6a105b
treecbd1ce98e6779a70e8d289dc0266f183f31ff7da
parentcca9f93a52d2ead50b5da59ca83d5f469ee4be5f
xfs: xfs_ifree doesn't need to modify the inode buffer

Long ago, bulkstat used to read inodes directly from the backing
buffer for speed. This had the unfortunate problem of being cache
incoherent with unlinks, and so xfs_ifree() had to mark the inode
as free directly in the backing buffer. bulkstat was changed some
time ago to use inode cache coherent lookups, and so will never see
unlinked inodes in it's lookups. Hence xfs_ifree() does not need to
touch the inode backing buffer anymore.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Mark Tinguely <tinguely@sgi.com>
Signed-off-by: Ben Myers <bpm@sgi.com>
fs/xfs/xfs_inode.c