btrfs-progs: fsck: Fix a false alert where extent record has wrong metadata flag
authorQu Wenruo <quwenruo@cn.fujitsu.com>
Wed, 25 Nov 2015 06:19:06 +0000 (14:19 +0800)
committerDavid Sterba <dsterba@suse.com>
Thu, 26 Nov 2015 14:15:38 +0000 (15:15 +0100)
commitb08a740d7b797d870cbc3691b1291290d0815998
treef4e4c8c715b9384179fd0029f860427453cd8b83
parent73a015578a5f51993645f87ba660372a0ec56997
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 <calestyo@scientia.net>
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
Signed-off-by: David Sterba <dsterba@suse.com>
cmds-check.c