summaryrefslogtreecommitdiffstats
path: root/fs/xfs/xfs_trans_dquot.c
diff options
context:
space:
mode:
authorDave Chinner <dchinner@redhat.com>2012-04-29 21:16:17 +1000
committerBen Myers <bpm@sgi.com>2012-05-14 16:20:38 -0500
commit58e20770646932fe9b758c94e8c278ea9ec93878 (patch)
treefbb2ef5941ee428c4739c68d5616b082e09790db /fs/xfs/xfs_trans_dquot.c
parent81158e0cecdf53b1f6d88a514c6c20e0ee18ec7b (diff)
downloadtalos-obmc-linux-58e20770646932fe9b758c94e8c278ea9ec93878.tar.gz
talos-obmc-linux-58e20770646932fe9b758c94e8c278ea9ec93878.zip
xfs: don't assert on delalloc regions beyond EOF
When we are doing speculative delayed allocation beyond EOF, conversion of the region allocated beyond EOF is dependent on the largest free space extent available. If the largest free extent is smaller than the delalloc range, then after allocation we leave a delalloc extent that starts beyond EOF. This extent cannot *ever* be converted by flushing data, and so will remain there until either the EOF moves into the extent or it is truncated away. Hence if xfs_getbmap() runs on such an inode and is asked to return extents beyond EOF, it will assert fail on this extent even though there is nothing xfs_getbmap() can do to convert it to a real extent. Hence we should simply report these delalloc extents rather than assert that there should be none. Signed-off-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Ben Myers <bpm@sgi.com>
Diffstat (limited to 'fs/xfs/xfs_trans_dquot.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud