linux-master/kernel/panic.c

3  *  linux/kernel/panic.c
143  * Stop ourself in panic -- architecture code may override this
161  * Stop other CPUs in panic.  Architecture dependent code may override this
171 	 * This function can be called twice in panic path, but obviously
179 	 * unfortunately means it may not be hardened to work in a panic
189  * A variant of panic() called from NMI context. We return if we've already
203 		panic("%s", msg);
241 		panic("%s: panic_on_warn set ...\n", origin);
245 		panic("%s: system warned too often (kernel.warn_limit is %d)",
261 	 * which unfortunately may not be hardened to work in a panic
274  *	panic - halt the system
281 void panic(const char *fmt, ...)
292 		 * This thread may hit another WARN() in the panic path.
295 		 * panic_mutex in panic().
302 	 * from deadlocking the first cpu that invokes the panic, since
304 	 * after setting panic_cpu) from invoking panic() again.
310 	 * It's possible to come here directly from a panic-assertion and
314 	 * Only one CPU is allowed to execute the panic code from here. For
315 	 * multiple parallel invocations of panic, all other CPUs either
342 	pr_emerg("Kernel panic - not syncing: %s\n", buf);
345 	 * Avoid nested stack-dumping if a panic occurs during oops processing
372 	 * Run any panic handlers, including those that might need to
401 	 * panic() is not being callled from OOPS.
449 	pr_emerg("---[ end Kernel panic - not syncing: %s ]---\n", buf);
472 EXPORT_SYMBOL(panic);
559 		panic("panic_on_taint set ...");
780 	panic("stack-protector: Kernel stack is corrupted in: %pB",
788 core_param(panic, panic_timeout, int, 0644);
798 	if (!strcmp(s, "panic"))