summaryrefslogtreecommitdiffstats
path: root/drivers/staging/android
diff options
context:
space:
mode:
authorStefan Behrens <sbehrens@giantdisaster.de>2013-09-05 16:58:43 +0200
committerChris Mason <chris.mason@fusionio.com>2013-11-11 21:49:26 -0500
commit69e9c6c6dc87587d8846e447febedefe037c14f8 (patch)
tree557fc35afdf3bbee9ce0f46a2ce16ce1c386133c /drivers/staging/android
parent5e01dc7b26d9f24f39abace5da98ccbd6a5ceb52 (diff)
downloadblackbird-obmc-linux-69e9c6c6dc87587d8846e447febedefe037c14f8.tar.gz
blackbird-obmc-linux-69e9c6c6dc87587d8846e447febedefe037c14f8.zip
Btrfs: eliminate the exceptional root_tree refs=0
The fact that btrfs_root_refs() returned 0 for the tree_root caused bugs in the past, therefore it is set to 1 with this patch and (hopefully) all affected code is adapted to this change. I verified this change by temporarily adding WARN_ON() checks everywhere where btrfs_root_refs() is used, checking whether the logic of the code is changed by btrfs_root_refs() returning 1 instead of 0 for root->root_key.objectid == BTRFS_ROOT_TREE_OBJECTID. With these added checks, I ran the xfstests './check -g auto'. The two roots chunk_root and log_root_tree that are only referenced by the superblock and the log_roots below the log_root_tree still have btrfs_root_refs() == 0, only the tree_root is changed. Signed-off-by: Stefan Behrens <sbehrens@giantdisaster.de> Signed-off-by: Josef Bacik <jbacik@fusionio.com> Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Diffstat (limited to 'drivers/staging/android')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud