btrfs: fix abort logic in btrfs_replace_file_extents
Error injection testing uncovered a case where we'd end up with a
corrupt file system with a missing extent in the middle of a file. This
occurs because the if statement to decide if we should abort is wrong.
The only way we would abort in this case is if we got a ret !=
-EOPNOTSUPP and we called from the file clone code. However the
prealloc code uses this path too. Instead we need to abort if there is
an error, and the only error we _don't_ abort on is -EOPNOTSUPP and only
if we came from the clone file code.
CC: email@example.com # 5.10+
Reviewed-by: Nikolay Borisov <firstname.lastname@example.org>
Reviewed-by: Filipe Manana <email@example.com>
Signed-off-by: Josef Bacik <firstname.lastname@example.org>
Reviewed-by: David Sterba <email@example.com>
Signed-off-by: David Sterba <firstname.lastname@example.org>
1 file changed