diff options
| author | Brian Behlendorf <[email protected]> | 2010-05-20 10:15:51 -0700 |
|---|---|---|
| committer | Brian Behlendorf <[email protected]> | 2010-05-20 10:15:51 -0700 |
| commit | 3626ae6a7008b2d4d16ddd01defd45a8d7aac3b8 (patch) | |
| tree | 5ad0b48b506f5de6b67d425b63bb4f23c7c66194 /module | |
| parent | e0dcb22e4ee6b7205e7cc1acd6de24d02509e9cc (diff) | |
Disable spl_debug_panic_on_bug by default.
While I may prefer to have the system panic on an SBUG and to get
crash dump for analysis. I suspect most peoples systems are not
configured from crash dump and the best thing to so is to simply
halt the thread and print an error to the console. This way they
have a good chance of actually saving the stack trace and debug log.
Diffstat (limited to 'module')
| -rw-r--r-- | module/spl/spl-debug.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/module/spl/spl-debug.c b/module/spl/spl-debug.c index 3d07a5647..8ee6c5dfb 100644 --- a/module/spl/spl-debug.c +++ b/module/spl/spl-debug.c @@ -71,7 +71,7 @@ EXPORT_SYMBOL(spl_debug_binary); unsigned int spl_debug_catastrophe; EXPORT_SYMBOL(spl_debug_catastrophe); -unsigned int spl_debug_panic_on_bug = 1; +unsigned int spl_debug_panic_on_bug = 0; EXPORT_SYMBOL(spl_debug_panic_on_bug); module_param(spl_debug_panic_on_bug, int, 0644); MODULE_PARM_DESC(spl_debug_panic_on_bug, "Panic on BUG"); |