diff options
| author | Jeff Mahoney <jeffm@suse.com> | 2011-10-04 07:22:31 +0400 |
|---|---|---|
| committer | David Sterba <dsterba@suse.cz> | 2012-03-22 04:45:29 +0400 |
| commit | 8c3429300181be44b30f9f017d53dc717da56caa (patch) | |
| tree | 76d2b3155bfff43ac4c96df7d6ccb723849c6e9f /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | c16fa4f2ad19908a47c63d8fa436a1178438c7e7 (diff) | |
| download | linux-8c3429300181be44b30f9f017d53dc717da56caa.tar.xz | |
btrfs: Add btrfs_panic()
As part of the effort to eliminate BUG_ON as an error handling
technique, we need to determine which errors are actual logic errors,
which are on-disk corruption, and which are normal runtime errors
e.g. -ENOMEM.
Annotating these error cases is helpful to understand and report them.
This patch adds a btrfs_panic() routine that will either panic
or BUG depending on the new -ofatal_errors={panic,bug} mount option.
Since there are still so many BUG_ONs, it defaults to BUG for now but I
expect that to change once the error handling effort has made
significant progress.
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions