Re: [PATCH] panic: call bust_spinlocks(0) before dying
From: Frédéric Weisbecker
Date: Fri Oct 02 2009 - 08:08:03 EST
2009/10/2 Aaro Koskinen <aaro.koskinen@xxxxxxxxx>:
> Commit ffd71da4e3f323b7673b061e6f7e0d0c12dc2b49 moved bust_spinlocks(0)
> to the end of the function, which in practice is never reached. As a
> result console_unblank() is not called, and on some systems the user
> may not see the panic message.
Indeed.
> Signed-off-by: Aaro Koskinen <aaro.koskinen@xxxxxxxxx>
> ---
> kernel/panic.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/panic.c b/kernel/panic.c
> index bcdef26..96b45d0 100644
> --- a/kernel/panic.c
> +++ b/kernel/panic.c
> @@ -90,6 +90,8 @@ NORET_TYPE void panic(const char * fmt, ...)
>
> atomic_notifier_call_chain(&panic_notifier_list, 0, buf);
>
> + bust_spinlocks(0);
> +
And it looks like the right place to do that. The rest that is going
to be displayed
is messages about countdown before reboot. The most important messages
have been printk'ed already.
Reviewed-by: Frederic Weisbecker <fweisbec@xxxxxxxxx>
> if (!panic_blink)
> panic_blink = no_blink;
>
> @@ -136,7 +138,6 @@ NORET_TYPE void panic(const char * fmt, ...)
> mdelay(1);
> i++;
> }
> - bust_spinlocks(0);
> }
>
> EXPORT_SYMBOL(panic);
> --
> 1.5.4.3
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/