btrfs: zoned: fix wrong mutex unlock on failure to allocate log root tree
authorFilipe Manana <fdmanana@suse.com>
Wed, 7 Jul 2021 11:23:45 +0000 (12:23 +0100)
committerDavid Sterba <dsterba@suse.com>
Wed, 7 Jul 2021 16:27:44 +0000 (18:27 +0200)
commitea32af47f00a046a1f953370514d6d946efe0152
tree9ee5fa709f00bd58b7e8210a40f80c27b51872e8
parent9cc0b837e14ae913581ec1ea6e979a738f71b0fd
btrfs: zoned: fix wrong mutex unlock on failure to allocate log root tree

When syncing the log, if we fail to allocate the root node for the log
root tree:

1) We are unlocking fs_info->tree_log_mutex, but at this point we have
   not yet locked this mutex;

2) We have locked fs_info->tree_root->log_mutex, but we end up not
   unlocking it;

So fix this by unlocking fs_info->tree_root->log_mutex instead of
fs_info->tree_log_mutex.

Fixes: e75f9fd194090e ("btrfs: zoned: move log tree node allocation out of log_root_tree->log_mutex")
CC: stable@vger.kernel.org # 5.13+
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/tree-log.c