diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2021-11-27 12:50:03 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2021-11-27 12:50:03 -0800 |
commit | adfb743ac0267de089c878d2f81be2facdcb4fe2 (patch) | |
tree | 4be4fa9e3848953c76b0d28e44f79ab2ad555b87 /fs/fat | |
parent | 86155d6b43ced7768b70e7b57bcf53a6fb6b1f2d (diff) | |
parent | 5ad448ce2976f829d95dcae5e6e91f6686b0e4de (diff) | |
download | linux-adfb743ac0267de089c878d2f81be2facdcb4fe2.tar.bz2 |
Merge tag 'iomap-5.16-fixes-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
Pull iomap fixes from Darrick Wong:
"A single iomap bug fix and a cleanup for 5.16-rc2.
The bug fix changes how iomap deals with reading from an inline data
region -- whereas the current code (incorrectly) lets the iomap read
iter try for more bytes after reading the inline region (which zeroes
the rest of the page!) and hopes the next iteration terminates, we
surveyed the inlinedata implementations and realized that all
inlinedata implementations also require that the inlinedata region end
at EOF, so we can simply terminate the read.
The second patch documents these assumptions in the code so that
they're not subtle implications anymore, and cleans up some of the
grosser parts of that function.
Summary:
- Fix an accounting problem where unaligned inline data reads can run
off the end of the read iomap iterator. iomap has historically
required that inline data mappings only exist at the end of a file,
though this wasn't documented anywhere.
- Document iomap_read_inline_data and change its return type to be
appropriate for the information that it's actually returning"
* tag 'iomap-5.16-fixes-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
iomap: iomap_read_inline_data cleanup
iomap: Fix inline extent handling in iomap_readpage
Diffstat (limited to 'fs/fat')
0 files changed, 0 insertions, 0 deletions