btrfs: Factor out common extent locking code in submit_compressed_extents
authorNikolay Borisov <nborisov@suse.com>
Tue, 12 Mar 2019 15:20:30 +0000 (17:20 +0200)
committerDavid Sterba <dsterba@suse.com>
Thu, 2 May 2019 11:48:19 +0000 (13:48 +0200)
commit7447555fe7765d7823f5db7760bfdeba035b7bad
treea390453fc43d1788dacce25bbdf885192832d580
parent4336650aff746e23d387227db826b39f00a3f3c3
btrfs: Factor out common extent locking code in submit_compressed_extents

Irrespective of whether the compress code fell back to uncompressed or
a compressed extent has to be submitted, the extent range is always
locked. So factor out the common lock_extent call at the beginning of
the loop. No functional changes just removes one duplicate lock_extent
call.

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>
fs/btrfs/inode.c