summaryrefslogtreecommitdiffstats
path: root/fs/zonefs
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2022-08-04 00:16:49 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2022-08-04 00:16:49 +0200
commitf18d73096c0eca1275f586cb984e6e28330447a0 (patch)
treed8c41b69e3f9373fcf0fbfad057d344db2dfd4a1 /fs/zonefs
parentMerge tag 'affs-5.20-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kd... (diff)
parentdax: set did_zero to true when zeroing successfully (diff)
downloadlinux-f18d73096c0eca1275f586cb984e6e28330447a0.tar.xz
linux-f18d73096c0eca1275f586cb984e6e28330447a0.zip
Merge tag 'iomap-5.20-merge-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
Pull iomap updates from Darrick Wong: "The most notable change in this first batch is that we no longer schedule pages beyond i_size for writeback, preferring instead to let truncate deal with those pages. Next week, there may be a second pull request to remove iomap_writepage from the other two filesystems (gfs2/zonefs) that use iomap for buffered IO. This follows in the same vein as the recent removal of writepage from XFS, since it hasn't been triggered in a few years; it does nothing during direct reclaim; and as far as the people who examined the patchset can tell, it's moving the codebase in the right direction. However, as it was a late addition to for-next, I'm holding off on that section for another week of testing to see if anyone can come up with a solid reason for holding off in the meantime. Summary: - Skip writeback for pages that are completely beyond EOF - Minor code cleanups" * tag 'iomap-5.20-merge-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux: dax: set did_zero to true when zeroing successfully iomap: set did_zero to true when zeroing successfully iomap: skip pages past eof in iomap_do_writepage()
Diffstat (limited to 'fs/zonefs')
0 files changed, 0 insertions, 0 deletions