diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2022-05-25 05:21:30 +0300 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2022-05-25 05:21:30 +0300 |
| commit | 8642174b52214dde4d8113f28fb4c9be5a432126 (patch) | |
| tree | ebeec25c212a976b5c80bb5995a2397f0b933744 /block | |
| parent | f289811258552a8a8c15d2446f9ead1d567357f2 (diff) | |
| parent | e9c3a8e820ed0eeb2be05072f29f80d1b79f053b (diff) | |
| download | linux-8642174b52214dde4d8113f28fb4c9be5a432126.tar.xz | |
Merge tag 'iomap-5.19-merge-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
Pull iomap updates from Darrick Wong:
"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.
Summary:
- 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"
* tag 'iomap-5.19-merge-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
iomap: don't invalidate folios after writeback errors
iomap: iomap_write_end cleanup
iomap: iomap_write_failed fix
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions