btrfs: abort in rename_exchange if we fail to insert the second ref

stable inclusion
from stable-v5.10.42
commit 0df50d47d17401f9f140dfbe752a65e5d72f9932
category: bugfix
bugzilla: https://gitee.com/src-openeuler/kernel/issues/I9909R
CVE: CVE-2021-47113

Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=tags/v5.10.43&id=0df50d47d17401f9f140dfbe752a65e5d72f9932



--------------------------------

commit dc09ef35 upstream.

Error injection stress uncovered a problem where we'd leave a dangling
inode ref if we failed during a rename_exchange.  This happens because
we insert the inode ref for one side of the rename, and then for the
other side.  If this second inode ref insert fails we'll leave the first
one dangling and leave a corrupt file system behind.  Fix this by
aborting if we did the insert for the first inode ref.

CC: stable@vger.kernel.org # 4.9+
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Conflicts:
	fs/btrfs/inode.c

Signed-off-by: Long Li <leo.lilong@huawei.com>