diff options
| author | Darrick J. Wong <[email protected]> | 2017-12-07 00:13:35 +0000 |
|---|---|---|
| committer | Darrick J. Wong <[email protected]> | 2017-12-09 01:51:05 +0000 |
| commit | b7e0b6ff54dd92febbb1914ab93cd6a21622e169 (patch) | |
| tree | ab08c84d8d224ca9f20731bdae9cb21d40e47a3b /net/tipc/node.c | |
| parent | xfs: remove "no-allocation" reservations for file creations (diff) | |
| download | kernel-b7e0b6ff54dd92febbb1914ab93cd6a21622e169.tar.gz kernel-b7e0b6ff54dd92febbb1914ab93cd6a21622e169.zip | |
xfs: make iomap_begin functions trim iomaps consistently
Historically, the XFS iomap_begin function only returned mappings for
exactly the range queried, i.e. it doesn't do XFS_BMAPI_ENTIRE lookups.
The current vfs iomap consumers are only set up to deal with trimmed
mappings. xfs_xattr_iomap_begin does BMAPI_ENTIRE lookups, which is
inconsistent with the current iomap usage. Remove the flag so that both
iomap_begin functions behave the same way.
FWIW this also fixes a behavioral regression in xattr FIEMAP that was
introduced in 4.8 wherein attr fork extents are no longer trimmed like
they used to be.
Signed-off-by: Darrick J. Wong <[email protected]>
Reviewed-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'net/tipc/node.c')
0 files changed, 0 insertions, 0 deletions