[PATCH 4/4] btrfs: Don't opencode sync_blockdev

Nikolay Borisov
2020-07-22T08:09:29Z

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

Signed-off-by: Nikolay Borisov <nborisov@suse.com>
---
fs/btrfs/volumes.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index 17047c118969..d42571f36fcf 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -2499,7 +2499,7 @@ int btrfs_init_new_device(struct btrfs_fs_info *fs_info, const char *device_path
locked = true;
}

- filemap_write_and_wait(bdev->bd_inode->i_mapping);
+ sync_blockdev(bdev);

rcu_read_lock();
list_for_each_entry_rcu(device, &fs_devices->devices, dev_list) {
--
2.17.1