diff options
author | 2013-04-23 10:53:18 -0400 | |
---|---|---|
committer | 2013-05-06 15:55:04 -0400 | |
commit | fb7669b5a0695922a9813bb103303db3d7c79c8d (patch) | |
tree | 67e96d7bf0f389932e04367f2235e8d6a11d26a3 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | Btrfs: don't call readahead hook until we have read the entire eb (diff) | |
download | linux-dev-fb7669b5a0695922a9813bb103303db3d7c79c8d.tar.xz linux-dev-fb7669b5a0695922a9813bb103303db3d7c79c8d.zip |
Btrfs: don't BUG_ON() in btrfs_num_copies
A user sent me a btrfs-image that was panicing because of some corruption. This
is because we pass in a bogus value to btrfs_num_copies, and it panics. Instead
just return 1. We only call btrfs_num_copies to see if there are other copies
to try and read for things, so if we just return 1 it will make the callers exit
out with an appropriate error value. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions