btrfs: Remove redundant FLAG_VACANCY
authorNikolay Borisov <nborisov@suse.com>
Thu, 23 Nov 2017 08:51:43 +0000 (10:51 +0200)
committerDavid Sterba <dsterba@suse.com>
Mon, 22 Jan 2018 15:08:14 +0000 (16:08 +0100)
commit4a2d25cd93cbd2e5ad6c9aabd90da362b2dd9984
tree85c1426042016b6a94d7e8d6bc27b04554588ebd
parent3f2dd7a0cef4d7ff964bb5e35beb500cbf3b7bcf
btrfs: Remove redundant FLAG_VACANCY

Commit 9036c10208e1 ("Btrfs: update hole handling v2") added the
FLAG_VACANCY to denote holes, however there was already a consistent way
of flagging extents which represent hole - ->block_start =
EXTENT_MAP_HOLE. And also the only place where this flag is checked is
in the fiemap code, but the block_start value is also checked and every
other place in the filesystem detects holes by using block_start
value's. So remove the extra flag. This survived a full xfstest run.

Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/extent_io.c
fs/btrfs/extent_map.h
fs/btrfs/inode.c
fs/btrfs/tests/inode-tests.c
include/trace/events/btrfs.h