aboutsummaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorJosef Bacik <jbacik@fusionio.com>2013-07-30 16:30:30 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-10-13 14:51:08 -0700
commit3609e1162ce723d3269924e95f2663d8bd72a537 (patch)
treeb74892ad919a6866dab5afe96e6a981ddca36162 /README
parenta9f1434b8e47776e2b6d42a5556516209f5ba3ae (diff)
downloadkernel_samsung_smdk4412-3609e1162ce723d3269924e95f2663d8bd72a537.zip
kernel_samsung_smdk4412-3609e1162ce723d3269924e95f2663d8bd72a537.tar.gz
kernel_samsung_smdk4412-3609e1162ce723d3269924e95f2663d8bd72a537.tar.bz2
Btrfs: change how we queue blocks for backref checking
commit b6c60c8018c4e9beb2f83fc82c09f9d033766571 upstream. Previously we only added blocks to the list to have their backrefs checked if the level of the block is right above the one we are searching for. This is because we want to make sure we don't add the entire path up to the root to the lists to make sure we process things one at a time. This assumes that if any blocks in the path to the root are going to be not checked (shared in other words) then they will be in the level right above the current block on up. This isn't quite right though since we can have blocks higher up the list that are shared because they are attached to a reloc root. But we won't add this block to be checked and then later on we will BUG_ON(!upper->checked). So instead keep track of wether or not we've queued a block to be checked in this current search, and if we haven't go ahead and queue it to be checked. This patch fixed the panic I was seeing where we BUG_ON(!upper->checked). Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> Signed-off-by: Chris Mason <chris.mason@fusionio.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions