xfs: Don't use reserved blocks for data blocks with DAX
authorDave Chinner <dchinner@redhat.com>
Mon, 4 Jan 2016 05:22:45 +0000 (16:22 +1100)
committerDave Chinner <david@fromorbit.com>
Mon, 4 Jan 2016 05:22:45 +0000 (16:22 +1100)
commit3b0fe47805802216087259b07de691ef47ff6fbc
tree9bcbb04535f71cc5a53bf28de88474def8836dd0
parent168309855a7d1e16db751e9c647119fe2d2dc878
xfs: Don't use reserved blocks for data blocks with DAX

Commit 1ca1915 ("xfs: Don't use unwritten extents for DAX") enabled
the DAX allocation call to dip into the reserve pool in case it was
converting unwritten extents rather than allocating blocks. This was
a direct copy of the unwritten extent conversion code, but had an
unintended side effect of allowing normal data block allocation to
use the reserve pool. Hence normal block allocation could deplete
the reserve pool and prevent unwritten extent conversion at ENOSPC,
hence violating fallocate guarantees on preallocated space.

Fix it by checking whether the incoming map from __xfs_get_blocks()
spans an unwritten extent and only use the reserve pool if the
allocation covers an unwritten extent.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
Tested-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/xfs/xfs_iomap.c