summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/volumes.c
diff options
context:
space:
mode:
authorNikolay Borisov <nborisov@suse.com>2018-12-17 10:36:02 +0200
committerDavid Sterba <dsterba@suse.com>2019-02-25 14:13:22 +0100
commit02a033df7a5ebf356d59eeabab1a37ca175e8b5b (patch)
tree7cfe0fe17e7bdcb3669c7c2eaed38e676fa33d39 /fs/btrfs/volumes.c
parentb8eeab7fced20169f5d8b4e3894e9e470fdf01ef (diff)
downloadlinux-stable-02a033df7a5ebf356d59eeabab1a37ca175e8b5b.tar.gz
linux-stable-02a033df7a5ebf356d59eeabab1a37ca175e8b5b.tar.bz2
linux-stable-02a033df7a5ebf356d59eeabab1a37ca175e8b5b.zip
btrfs: Remove not_found_em label from btrfs_get_extent
In order to avoid duplicating init code for em there is an additional label, not_found_em, which is used to only set ->block_start. The only case when it will be used is if the extent we are adding overlaps with an existing extent. Make that case more obvious by: 1. Adding a comment hinting at what's going on 2. Assigning EXTENT_MAP_HOLE and directly going to insert. No functional changes. Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de> 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 'fs/btrfs/volumes.c')
0 files changed, 0 insertions, 0 deletions