Hi Linus,
Please pull this branch containing all the new code for iomap for
5.19. There's a couple of corrections sent in by Andreas for some
accounting errors.
The biggest change this time around is that writeback errors longer
clear pageuptodate nor does XFS invalidate the page cache anymore. This
brings XFS (and gfs2/zonefs) behavior in line with every other Linux
filesystem driver, and fixes some UAF bugs that only cropped up after
willy turned on multipage folios for XFS in 5.18-rc1. Regrettably, it
took all the way to the end of the 5.18 cycle to find the source of
these bugs and reach a consensus that XFS' writeback failure behavior
from 20 years ago is no longer necessary.
As usual, I did a test-merge with upstream master as of a few minutes
ago, and didn't see any conflicts. Please let me know if you encounter
any problems.
--D
The following changes since commit c5eb0a61238dd6faf37f58c9ce61c9980aaffd7a:
Linux 5.18-rc6 (2022-05-08 13:54:17 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/iomap-5.19-merge-2
for you to fetch changes up to e9c3a8e820ed0eeb2be05072f29f80d1b79f053b:
iomap: don't invalidate folios after writeback errors (2022-05-16 15:27:38 -0700)
----------------------------------------------------------------
New code for 5.19:
- Fix a couple of accounting errors in the buffered io code.
- Discontinue the practice of marking folios !uptodate and invalidating
them when writeback fails. This fixes some UAF bugs when multipage
folios are enabled, and brings the behavior of XFS/gfs/zonefs into
alignment with the behavior of all the other Linux filesystems.
----------------------------------------------------------------
Andreas Gruenbacher (2):
iomap: iomap_write_failed fix
iomap: iomap_write_end cleanup
Darrick J. Wong (1):
iomap: don't invalidate folios after writeback errors
fs/iomap/buffered-io.c | 6 +++---
fs/xfs/xfs_aops.c | 4 +---
2 files changed, 4 insertions(+), 6 deletions(-)
