btrfs: deal with errors when adding inode reference during log replay
authorFilipe Manana <fdmanana@suse.com>
Fri, 1 Oct 2021 12:52:32 +0000 (13:52 +0100)
committerDavid Sterba <dsterba@suse.com>
Thu, 7 Oct 2021 20:06:30 +0000 (22:06 +0200)
commit52db77791fe24538c8aa2a183248399715f6b380
treeeb7e248ad88698709bec79cc3762d6c29b63ccac
parente15ac6413745e3def00e663de00aea5a717311c1
btrfs: deal with errors when adding inode reference during log replay

At __inode_add_ref(), we treating any error returned from
btrfs_lookup_dir_item() or from btrfs_lookup_dir_index_item() as meaning
that there is no existing directory entry in the fs/subvolume tree.
This is not correct since we can get errors such as, for example, -EIO
when reading extent buffers while searching the fs/subvolume's btree.

So fix that and return the error to the caller when it is not -ENOENT.

CC: stable@vger.kernel.org # 4.14+
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/tree-log.c