]> git.ipfire.org Git - thirdparty/xfsprogs-dev.git/commit
xfs: fix COW writeback race
authorChristoph Hellwig <hch@lst.de>
Thu, 16 Feb 2017 03:03:54 +0000 (21:03 -0600)
committerEric Sandeen <sandeen@redhat.com>
Thu, 16 Feb 2017 03:03:54 +0000 (21:03 -0600)
commit7075a23fc770ada904e1795bb0b44c0c36942ed2
tree322f1375d6b2e7c69b876fad66ba76419edc8f21
parent5b1caea4aaa66e5c32de8bc84ebf516144f5c165
xfs: fix COW writeback race

Source kernel commit: d2b3964a0780d2d2994eba57f950d6c9fe489ed8

Due to the way how xfs_iomap_write_allocate tries to convert the whole
found extents from delalloc to real space we can run into a race
condition with multiple threads doing writes to this same extent.
For the non-COW case that is harmless as the only thing that can happen
is that we call xfs_bmapi_write on an extent that has already been
converted to a real allocation.  For COW writes where we move the extent
from the COW to the data fork after I/O completion the race is, however,
not quite as harmless.  In the worst case we are now calling
xfs_bmapi_write on a region that contains hole in the COW work, which
will trip up an assert in debug builds or lead to file system corruption
in non-debug builds.  This seems to be reproducible with workloads of
small O_DSYNC write, although so far I've not managed to come up with
a with an isolated reproducer.

The fix for the issue is relatively simple:  tell xfs_bmapi_write
that we are only asked to convert delayed allocations and skip holes
in that case.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
libxfs/xfs_bmap.c
libxfs/xfs_bmap.h