summaryrefslogtreecommitdiffstats
path: root/scripts/analyze_suspend.py
diff options
context:
space:
mode:
authorJosef Bacik2014-09-19 16:40:00 +0200
committerChris Mason2014-10-04 01:14:58 +0200
commit75bfb9aff45e44625260f52a5fd581b92ace3e62 (patch)
tree32fc26b1b21a237ed5e864b9fd94990a9b23932d /scripts/analyze_suspend.py
parentBtrfs: try not to ENOSPC on log replay (diff)
downloadkernel-qcow2-linux-75bfb9aff45e44625260f52a5fd581b92ace3e62.tar.gz
kernel-qcow2-linux-75bfb9aff45e44625260f52a5fd581b92ace3e62.tar.xz
kernel-qcow2-linux-75bfb9aff45e44625260f52a5fd581b92ace3e62.zip
Btrfs: cleanup error handling in build_backref_tree
When balance panics it tends to panic in the BUG_ON(!upper->checked); test, because it means it couldn't build the backref tree properly. This is annoying to users and frankly a recoverable error, nothing in this function is actually fatal since it is just an in-memory building of the backrefs for a given bytenr. So go through and change all the BUG_ON()'s to ASSERT()'s, and fix the BUG_ON(!upper->checked) thing to just return an error. This patch also fixes the error handling so it tears down the work we've done properly. This code was horribly broken since we always just panic'ed instead of actually erroring out, so it needed to be completely re-worked. With this patch my broken image no longer panics when I mount it. Thanks, Signed-off-by: Josef Bacik <jbacik@fb.com> Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'scripts/analyze_suspend.py')
0 files changed, 0 insertions, 0 deletions