On Tue, 15 Jul 2025 13:21:17 -0700, Joanne Koong wrote: > This series adds fuse iomap support for buffered writes and dirty folio > writeback. This is needed so that granular uptodate and dirty tracking can > be used in fuse when large folios are enabled. This has two big advantages. > For writes, instead of the entire folio needing to be read into the page > cache, only the relevant portions need to be. For writeback, only the > dirty portions need to be written back instead of the entire folio. > > [...] Applied to the vfs-6.17.iomap branch of the vfs/vfs.git tree. Patches in the vfs-6.17.iomap 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-6.17.iomap [1/5] fuse: use iomap for buffered writes https://git.kernel.org/vfs/vfs/c/a4c9ab1d4975 [2/5] fuse: use iomap for writeback https://git.kernel.org/vfs/vfs/c/ef7e7cbb323f [3/5] fuse: use iomap for folio laundering https://git.kernel.org/vfs/vfs/c/1097a87dcb74 [4/5] fuse: hook into iomap for invalidating and checking partial uptodateness https://git.kernel.org/vfs/vfs/c/707c5d3471e3 [5/5] fuse: refactor writeback to use iomap_writepage_ctx inode https://git.kernel.org/vfs/vfs/c/6e2f4d8a6118
