btrfs: don't opencode sync_blockdev in btrfs_init_new_device
authorNikolay Borisov <nborisov@suse.com>
Wed, 22 Jul 2020 08:09:25 +0000 (11:09 +0300)
committerDavid Sterba <dsterba@suse.com>
Wed, 7 Oct 2020 10:12:15 +0000 (12:12 +0200)
commitb9ba017fb0771f67903d70f57908899d7b0020b1
treea022f6b31a97dae8caa645d554f2812e85f09133
parent4ae312e9728fe568ce0d863421c399ec829d6df9
btrfs: don't opencode sync_blockdev in btrfs_init_new_device

Instead of opencoding filemap_write_and_wait simply call syncblockdev as
it makes it abundantly clear what's going on and why this is used. No
semantics changes.

Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Reviewed-by: Anand Jain <anand.jain@oracle.com>
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/volumes.c