diff options
| author | Qu Wenruo <quwenruo@cn.fujitsu.com> | 2017-06-22 04:01:21 +0200 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2017-06-29 20:25:20 +0200 |
| commit | 848c23b78fafdcd3270b06a30737f8dbd70c347f (patch) | |
| tree | 21a9247ef8e9070e818e62bb0e47ae4c08ecfc1f /fs/btrfs/raid56.c | |
| parent | btrfs: Don't clear SGID when inheriting ACLs (diff) | |
| download | linux-848c23b78fafdcd3270b06a30737f8dbd70c347f.tar.xz linux-848c23b78fafdcd3270b06a30737f8dbd70c347f.zip | |
btrfs: Remove false alert when fiemap range is smaller than on-disk extent
Commit 4751832da990 ("btrfs: fiemap: Cache and merge fiemap extent before
submit it to user") introduced a warning to catch unemitted cached
fiemap extent.
However such warning doesn't take the following case into consideration:
0 4K 8K
|<---- fiemap range --->|
|<----------- On-disk extent ------------------>|
In this case, the whole 0~8K is cached, and since it's larger than
fiemap range, it break the fiemap extent emit loop.
This leaves the fiemap extent cached but not emitted, and caught by the
final fiemap extent sanity check, causing kernel warning.
This patch removes the kernel warning and renames the sanity check to
emit_last_fiemap_cache() since it's possible and valid to have cached
fiemap extent.
Reported-by: David Sterba <dsterba@suse.cz>
Reported-by: Adam Borowski <kilobyte@angband.pl>
Fixes: 4751832da990 ("btrfs: fiemap: Cache and merge fiemap extent ...")
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/raid56.c')
0 files changed, 0 insertions, 0 deletions