summaryrefslogtreecommitdiffstats
path: root/fs/xfs/libxfs/xfs_sb.c
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2017-01-20 18:31:54 +0100
committerDarrick J. Wong <darrick.wong@oracle.com>2017-01-23 19:55:07 +0100
commitd2b3964a0780d2d2994eba57f950d6c9fe489ed8 (patch)
treee5431a683b41059abd0032aa46685ae78d766a50 /fs/xfs/libxfs/xfs_sb.c
parentLinux 4.10-rc5 (diff)
downloadlinux-d2b3964a0780d2d2994eba57f950d6c9fe489ed8.tar.xz
linux-d2b3964a0780d2d2994eba57f950d6c9fe489ed8.zip
xfs: fix COW writeback race
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>
Diffstat (limited to 'fs/xfs/libxfs/xfs_sb.c')
0 files changed, 0 insertions, 0 deletions