diff options
author | Nikolay Borisov <nborisov@suse.com> | 2017-11-23 10:51:43 +0200 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2018-01-22 16:08:14 +0100 |
commit | 4a2d25cd93cbd2e5ad6c9aabd90da362b2dd9984 (patch) | |
tree | 85c1426042016b6a94d7e8d6bc27b04554588ebd /Documentation/nommu-mmap.txt | |
parent | 3f2dd7a0cef4d7ff964bb5e35beb500cbf3b7bcf (diff) | |
download | linux-stable-4a2d25cd93cbd2e5ad6c9aabd90da362b2dd9984.tar.gz linux-stable-4a2d25cd93cbd2e5ad6c9aabd90da362b2dd9984.tar.bz2 linux-stable-4a2d25cd93cbd2e5ad6c9aabd90da362b2dd9984.zip |
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>
Diffstat (limited to 'Documentation/nommu-mmap.txt')
0 files changed, 0 insertions, 0 deletions