public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Bernhard Walle <bernhard@bwalle.de>
Cc: linux-kernel@vger.kernel.org, bernhard@bwalle.de
Subject: Re: [PATCH] Always print panic message on current console
Date: Tue, 29 Sep 2009 14:07:01 -0700	[thread overview]
Message-ID: <20090929140701.540f978b.akpm@linux-foundation.org> (raw)
In-Reply-To: <1254055014-4441-1-git-send-email-bernhard@bwalle.de>

On Sun, 27 Sep 2009 14:36:54 +0200
Bernhard Walle <bernhard@bwalle.de> wrote:

> The kernel offers with TIOCL_GETKMSGREDIRECT ioctl() the possibility to
> redirect the kernel messages to a specific console.
> 
> However, since it's not possible to switch to the kernel message console after
> a panic(), it would be nice if the kernel would print the panic message on the
> current console.
> 
> 
> Signed-off-by: Bernhard Walle <bernhard@bwalle.de>
> ---
>  kernel/panic.c |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/kernel/panic.c b/kernel/panic.c
> index bcdef26..f9950e3 100644
> --- a/kernel/panic.c
> +++ b/kernel/panic.c
> @@ -22,6 +22,7 @@
>  #include <linux/init.h>
>  #include <linux/nmi.h>
>  #include <linux/dmi.h>
> +#include <linux/tty.h>

It's odd that kmsg_redirect is declared in tty.h when it's purely a
vt.c thing.  Why not vt.h?

>  int panic_on_oops;
>  static unsigned long tainted_mask;
> @@ -65,6 +66,9 @@ NORET_TYPE void panic(const char * fmt, ...)
>  	 */
>  	preempt_disable();
>  
> +	/* don't redirect the panic message to some hidden console */
> +	kmsg_redirect = 0;
> +
>  	bust_spinlocks(1);
>  	va_start(args, fmt);
>  	vsnprintf(buf, sizeof(buf), fmt, args);

Methinks CONFIG_HW_CONSOLE=n kernels won't link after making this
change.

I'd suggest something like

#ifdef CONFIG_HW_CONSOLE
extern void vt_set_kmsg_redirect(int vt);
#else
static inline void vt_set_kmsg_redirect(int vt)
{
}
#endif


Another possible way of doing this would be for vt.c to hook itself
into panic_notifier_list.  That's nice and clean from a
separation-of-subsystems POV but isn't really conceptually correct - it
assumes that other entries on panic_notifier_list don't print messages
to the console.



  reply	other threads:[~2009-09-29 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-27 12:36 [PATCH] Always print panic message on current console Bernhard Walle
2009-09-29 21:07 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-30 13:59 Bernhard Walle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090929140701.540f978b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bernhard@bwalle.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox