summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_shutdown.c
diff options
context:
space:
mode:
authoravg <avg@FreeBSD.org>2011-07-25 09:12:48 +0000
committeravg <avg@FreeBSD.org>2011-07-25 09:12:48 +0000
commit50b05401d3190631fb48430b4c0b48789f259b8d (patch)
treeff97ee9903ea140928fcd9303e0d93873d3c2d2e /sys/kern/kern_shutdown.c
parentffeefed9fc8fa85d3fcbd19640ba38e51e2ff4da (diff)
downloadFreeBSD-src-50b05401d3190631fb48430b4c0b48789f259b8d.zip
FreeBSD-src-50b05401d3190631fb48430b4c0b48789f259b8d.tar.gz
remove RESTARTABLE_PANICS option
This is done per request/suggestion from John Baldwin who introduced the option. Trying to resume normal system operation after a panic is very unpredictable and dangerous. It will become even more dangerous when we allow a thread in panic(9) to penetrate all lock contexts. I understand that the only purpose of this option was for testing scenarios potentially resulting in panic. Suggested by: jhb Reviewed by: attilio, jhb X-MFC-After: never Approved by: re (kib)
Diffstat (limited to 'sys/kern/kern_shutdown.c')
-rw-r--r--sys/kern/kern_shutdown.c9
1 files changed, 0 insertions, 9 deletions
diff --git a/sys/kern/kern_shutdown.c b/sys/kern/kern_shutdown.c
index 60e854f..7621b15 100644
--- a/sys/kern/kern_shutdown.c
+++ b/sys/kern/kern_shutdown.c
@@ -585,15 +585,6 @@ panic(const char *fmt, ...)
kdb_backtrace();
if (debugger_on_panic)
kdb_enter(KDB_WHY_PANIC, "panic");
-#ifdef RESTARTABLE_PANICS
- /* See if the user aborted the panic, in which case we continue. */
- if (panicstr == NULL) {
-#ifdef SMP
- atomic_store_rel_int(&panic_cpu, NOCPU);
-#endif
- return;
- }
-#endif
#endif
/*thread_lock(td); */
td->td_flags |= TDF_INPANIC;
OpenPOWER on IntegriCloud