diff options
author | 2020-03-11 11:21:44 -0400 | |
---|---|---|
committer | 2020-03-23 17:01:56 +0100 | |
commit | b39c8f5a393e7fc4459ac2aa1582409839eae2f6 (patch) | |
tree | c5b4099483d36bdcf36fdf29de04e77d9d1dd9ca /tools/perf/scripts/python/export-to-postgresql.py | |
parent | btrfs: make ranged full fsyncs more efficient (diff) | |
download | linux-dev-b39c8f5a393e7fc4459ac2aa1582409839eae2f6.tar.xz linux-dev-b39c8f5a393e7fc4459ac2aa1582409839eae2f6.zip |
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>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions