tree c5b4099483d36bdcf36fdf29de04e77d9d1dd9ca
parent 0a8068a3dd4294ebd8b99969cdc6ccde0f944ba6
author Josef Bacik <josef@toxicpanda.com> 1583940104 -0400
committer David Sterba <dsterba@suse.com> 1584979316 +0100

btrfs: fix ref-verify to catch operations on 0 ref extents

While debugging I noticed I wasn't getting ref verify errors before
everything blew up.  Turns out it's because we don't warn when we try to
add a normal ref via btrfs_inc_ref() if the block entry exists but has 0
references.  This is incorrect, we should never be doing anything other
than adding a new extent once a block entry drops to 0 references.

Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>