On Mon, Oct 07, 2024 at 01:52:18PM +0200, Christian Brauner wrote: > On Thu, 03 Oct 2024 08:08:55 -0700, Darrick J. Wong wrote: > > This patchset fixes multiple data corruption bugs in the fallocate unshare > > range implementation for fsdax. > > > > With a bit of luck, this should all go splendidly. > > Comments and questions are, as always, welcome. > > > > --D > > > > [...] > > Applied to the vfs.iomap branch of the vfs/vfs.git tree. > Patches in the vfs.iomap branch should appear in linux-next soon. Er, this has been soaking for 18 days, is it going in soon? (Apologies, I just saw that you've been under the weather.) --D > Please report any outstanding bugs that were missed during review in a > new review to the original patch series allowing us to drop it. > > It's encouraged to provide Acked-bys and Reviewed-bys even though the > patch has now been applied. If possible patch trailers will be updated. > > Note that commit hashes shown below are subject to change due to rebase, > trailer updates or similar. If in doubt, please check the listed branch. > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git > branch: vfs.iomap > > [1/4] xfs: don't allocate COW extents when unsharing a hole > https://git.kernel.org/vfs/vfs/c/b8c4076db5fd > [2/4] iomap: share iomap_unshare_iter predicate code with fsdax > https://git.kernel.org/vfs/vfs/c/6ef6a0e821d3 > [3/4] fsdax: remove zeroing code from dax_unshare_iter > https://git.kernel.org/vfs/vfs/c/95472274b6fe > [4/4] fsdax: dax_unshare_iter needs to copy entire blocks > https://git.kernel.org/vfs/vfs/c/50793801fc7f >
