diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2020-08-06 19:35:12 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2020-08-06 19:35:12 -0700 |
commit | 0e4656a299db8484933a143259e7e5ebae2e3a01 (patch) | |
tree | 8f44153b771b4e1b04ebcdaae13d03a16bcd8a15 /net/dccp | |
parent | eb65405eb6860935d54b8ba90a5e231e07378be1 (diff) | |
parent | 60263d5889e6dc5987dc51b801be4955ff2e4aa7 (diff) |
Merge tag 'iomap-5.9-merge-5' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
Pull iomap updates from Darrick Wong:
"The most notable changes are:
- iomap no longer invalidates the page cache when performing a direct
read, since doing so is unnecessary and the old directio code
doesn't do that either.
- iomap embraced the use of returning ENOTBLK from a direct write to
trigger falling back to a buffered write since ext4 already did
this and btrfs wants it for their port.
- iomap falls back to buffered writes if we're doing a direct write
and the page cache invalidation after the flush fails; this was
necessary to handle a corner case in the btrfs port.
- Remove email virus scanner detritus that was accidentally included
in yesterday's pull request. Clearly I need(ed) to update my git
branch checker scripts. :("
* tag 'iomap-5.9-merge-5' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
iomap: fall back to buffered writes for invalidation failures
xfs: use ENOTBLK for direct I/O to buffered I/O fallback
iomap: Only invalidate page cache pages on direct IO writes
iomap: Make sure iomap_end is called after iomap_begin
Diffstat (limited to 'net/dccp')
0 files changed, 0 insertions, 0 deletions