summaryrefslogtreecommitdiffstats
path: root/block/blk-mq-cpu.c
diff options
context:
space:
mode:
authorLiu Bo <bo.li.liu@oracle.com>2015-07-28 18:03:30 +0800
committerChris Mason <clm@fb.com>2015-08-09 07:33:50 -0700
commitacdf898de8903f50bb10bbce4b774432bcd63c85 (patch)
tree79d2c35cc5ec383bb0edff3ec5c116b4c902622b /block/blk-mq-cpu.c
parent166f66d0bc94a14ec4bc6ee6ab079532df4a8d9e (diff)
downloadlinux-acdf898de8903f50bb10bbce4b774432bcd63c85.tar.bz2
Btrfs: fix warning in backref walking
When we do backref walking, we search firstly in queued delayed refs and then the on-disk backrefs, but we parse differently for shared references, for delayed refs we also add 'ref->root' while for on-disk backrefs we don't, this can prevent us from merging refs indexed by the same bytenr and cause find_parent_nodes() to throw a warning at 'WARN_ON(ref->count < 0)', for example, when we have a shared data extent with 'ref_cnt=1' and a delayed shared data with a BTRFS_DROP_DELAYED_REF, that happens. For shared references, no matter if it's delayed or on-disk, ref->root is not at all used, instead it's ref->parent that really matters, so this has delayed refs handled as the same way as on-disk refs. Signed-off-by: Liu Bo <bo.li.liu@oracle.com> Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'block/blk-mq-cpu.c')
0 files changed, 0 insertions, 0 deletions