On Fri, 30 Aug 2024 10:56:32 -0400, Brian Foster wrote: > Here's v3 of the iomap zero range flush fixes. No real changes here > other than comment updates to better explain the flush and stale logic. > The latest version of corresponding test support is posted here [1]. > Thoughts, reviews, flames appreciated. > > v3: > - Rework comment(s) in patch 2 to explain marking the mapping stale. > - Added R-b tags. > v2: https://lore.kernel.org/linux-fsdevel/20240828181912.41517-1-bfoster@xxxxxxxxxx/ > - Update comment in patch 2 to explain hole case. > v1: https://lore.kernel.org/linux-fsdevel/20240822145910.188974-1-bfoster@xxxxxxxxxx/ > - Alternative approach, flush instead of revalidate. > rfc: https://lore.kernel.org/linux-fsdevel/20240718130212.23905-1-bfoster@xxxxxxxxxx/ > > [...] Applied to the vfs.blocksize branch of the vfs/vfs.git tree. Patches in the vfs.blocksize branch should appear in linux-next soon. 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.blocksize [1/2] iomap: fix handling of dirty folios over unwritten extents https://git.kernel.org/vfs/vfs/c/e19d398f4eb8 [2/2] iomap: make zero range flush conditional on unwritten mappings https://git.kernel.org/vfs/vfs/c/2dbdb9dbad46
