From b08a740d7b797d870cbc3691b1291290d0815998 Mon Sep 17 00:00:00 2001 From: Qu Wenruo Date: Wed, 25 Nov 2015 14:19:06 +0800 Subject: btrfs-progs: fsck: Fix a false alert where extent record has wrong metadata flag In process_extent_item(), it gives 'metadata' initial value 0, but for non-skinny-metadata case, metadata extent can't be judged just from key type and it forgot that case. This causes a lot of false alert in non-skinny-metadata filesystem. Fix it by set correct metadata value before calling add_extent_rec(). Reported-by: Christoph Anton Mitterer Signed-off-by: Qu Wenruo Signed-off-by: David Sterba --- cmds-check.c | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'cmds-check.c') diff --git a/cmds-check.c b/cmds-check.c index 6a0b50a..b45412d 100644 --- a/cmds-check.c +++ b/cmds-check.c @@ -5134,6 +5134,10 @@ static int process_extent_item(struct btrfs_root *root, ei = btrfs_item_ptr(eb, slot, struct btrfs_extent_item); refs = btrfs_extent_refs(eb, ei); + if (btrfs_extent_flags(eb, ei) & BTRFS_EXTENT_FLAG_TREE_BLOCK) + metadata = 1; + else + metadata = 0; add_extent_rec(extent_cache, NULL, 0, key.objectid, num_bytes, refs, 0, 0, 0, metadata, 1, num_bytes); -- cgit v1.2.1