On Fri, 19 Jul 2024 15:20:18 +0100, David Howells wrote: > When netfslib is performing writeback (ie. ->writepages), it maintains two > parallel streams of writes, one to the server and one to the cache, but it > doesn't mark either stream of writes as active until it gets some data that > needs to be written to that stream. > > This is done because some folios will only be written to the cache > (e.g. copying to the cache on read is done by marking the folios and > letting writeback do the actual work) and sometimes we'll only be writing > to the server (e.g. if there's no cache). > > [...] Applied to the vfs.fixes branch of the vfs/vfs.git tree. Patches in the vfs.fixes 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.fixes [1/1] netfs: Fix writeback that needs to go to both server and cache https://git.kernel.org/vfs/vfs/c/55e81a4aa9ae
