Commit 16edae52 authored by Filipe Manana's avatar Filipe Manana Committed by David Sterba
Browse files

btrfs: don't silently ignore unexpected extent type when replaying log 



If there's an unexpected (invalid) extent type, we just silently ignore
it. This means a corruption or some bug somewhere, so instead return
-EUCLEAN to the caller, making log replay fail, and print an error message
with relevant information.

Reviewed-by: default avatarBoris Burkov <boris@bur.io>
Signed-off-by: default avatarFilipe Manana <fdmanana@suse.com>
Reviewed-by: default avatarDavid Sterba <dsterba@suse.com>
Signed-off-by: default avatarDavid Sterba <dsterba@suse.com>
parent 2dcf838c

fs/btrfs/tree-log.c

+4 −1
Original line number Diff line number Diff line
@@ -668,7 +668,10 @@ static noinline int replay_one_extent(struct btrfs_trans_handle *trans, 
		extent_end = ALIGN(start + size,

				   fs_info->sectorsize);

	} else {

		return 0;

		btrfs_err(fs_info,

		  "unexpected extent type=%d root=%llu inode=%llu offset=%llu",

			  found_type, btrfs_root_id(root), key->objectid, key->offset);

		return -EUCLEAN;

	}



	inode = read_one_inode(root, key->objectid);