Files
tegra-linux-noble/kernel
Ingo Molnar ffd71da4e3 panic: decrease oops_in_progress only after having done the panic
Impact: eliminate secondary warnings during panic()

We can panic() in a number of difficult, atomic contexts, hence
we use bust_spinlocks(1) in panic() to increase oops_in_progress,
which prevents various debug checks we have in place.

But in practice this protection only covers the first few printk's
done by panic() - it does not cover the later attempt to stop all
other CPUs and kexec(). If a secondary warning triggers in one of
those facilities that can make the panic message scroll off.

So do bust_spinlocks(0) only much later in panic(). (which code
is only reached if panic policy is relaxed that it can return
after a warning message)

Reported-by: Jan Beulich <jbeulich@novell.com>
LKML-Reference: <49B91A7E.76E4.0078.0@novell.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-03-13 11:06:47 +01:00
..
2009-02-08 10:00:26 -08:00
2009-02-18 15:37:54 -08:00
2009-02-13 09:44:22 +01:00
2009-02-11 18:24:08 +01:00
2009-02-22 20:05:19 +01:00
2009-01-06 15:59:27 -08:00
2008-12-10 08:01:54 -08:00
2009-02-21 14:17:17 -08:00
2009-01-08 08:31:02 -08:00
2009-01-08 08:31:12 -08:00
2009-01-06 11:07:15 +01:00
2008-11-05 10:30:14 +01:00
2009-03-13 11:05:58 +01:00