All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	pmladek@suse.com, kernel@gpiccoli.net, senozhatsky@chromium.org,
	rostedt@goodmis.org, john.ogness@linutronix.de,
	feng.tang@intel.com, kexec@lists.infradead.org,
	dyoung@redhat.com, keescook@chromium.org, anton@enomsg.org,
	ccross@android.com, tony.luck@intel.com
Subject: Re: [PATCH V3] panic: Move panic_print before kmsg dumpers
Date: Mon, 17 Jan 2022 14:13:15 +0800	[thread overview]
Message-ID: <20220117061315.GF2388@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220117033344.GA2523@MiWiFi-R3L-srv>

On 01/17/22 at 11:33am, Baoquan He wrote:
> On 01/14/22 at 03:30pm, Guilherme G. Piccoli wrote:
> ...... 
> >  .../admin-guide/kernel-parameters.txt         |  4 ++++
> >  kernel/panic.c                                | 22 ++++++++++++++-----
> >  2 files changed, 21 insertions(+), 5 deletions(-)
> > 
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> > index a069d8fe2fee..0f5cbe141bfd 100644
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -3727,6 +3727,10 @@
> >  			bit 4: print ftrace buffer
> >  			bit 5: print all printk messages in buffer
> >  			bit 6: print all CPUs backtrace (if available in the arch)
> > +			*Be aware* that this option may print a _lot_ of lines,
> > +			so there are risks of losing older messages in the log.
> > +			Use this option carefully, maybe worth to setup a
> > +			bigger log buffer with "log_buf_len" along with this.
> >  
> >  	panic_on_taint=	Bitmask for conditionally calling panic() in add_taint()
> >  			Format: <hex>[,nousertaint]
> > diff --git a/kernel/panic.c b/kernel/panic.c
> > index 41ecf9ab824a..4ae712665f75 100644
> > --- a/kernel/panic.c
> > +++ b/kernel/panic.c
> > @@ -148,10 +148,13 @@ void nmi_panic(struct pt_regs *regs, const char *msg)
> >  }
> >  EXPORT_SYMBOL(nmi_panic);
> >  
> > -static void panic_print_sys_info(void)
> > +static void panic_print_sys_info(bool after_kmsg_dumpers)
> >  {
> > -	if (panic_print & PANIC_PRINT_ALL_PRINTK_MSG)
> > -		console_flush_on_panic(CONSOLE_REPLAY_ALL);
> > +	if (after_kmsg_dumpers) {
> > +		if (panic_print & PANIC_PRINT_ALL_PRINTK_MSG)
> > +			console_flush_on_panic(CONSOLE_REPLAY_ALL);
> > +		return;
> > +	}
> >  
> >  	if (panic_print & PANIC_PRINT_ALL_CPU_BT)
> >  		trigger_all_cpu_backtrace();
> > @@ -249,7 +252,7 @@ void panic(const char *fmt, ...)
> >  	 * show some extra information on kernel log if it was set...
> >  	 */
> >  	if (kexec_crash_loaded())
> > -		panic_print_sys_info();
> > +		panic_print_sys_info(false);
> 
> Patch can'e be applied on the latest code of linus's tree, can you tell
> which branch your code are based on?

OK, this is based on linux-next, I will apply this patch on the
linux-next/master and have a look.

> 
> >  
> >  	/*
> >  	 * If we have crashed and we have a crash kernel loaded let it handle
> > @@ -283,6 +286,15 @@ void panic(const char *fmt, ...)
> >  	 */
> >  	atomic_notifier_call_chain(&panic_notifier_list, 0, buf);
> >  
> > +	/*
> > +	 * If kexec_crash_loaded() is true and we still reach this point,
> > +	 * kernel would double print the information from panic_print; so
> > +	 * let's guard against that possibility (it happens if kdump users
> > +	 * also set crash_kexec_post_notifiers in the command-line).
> > +	 */
> > +	if (!kexec_crash_loaded())
> > +		panic_print_sys_info(false);
> > +
> >  	kmsg_dump(KMSG_DUMP_PANIC);
> >  
> >  	/*
> > @@ -313,7 +325,7 @@ void panic(const char *fmt, ...)
> >  	debug_locks_off();
> >  	console_flush_on_panic(CONSOLE_FLUSH_PENDING);
> >  
> > -	panic_print_sys_info();
> > +	panic_print_sys_info(true);
> >  
> >  	if (!panic_blink)
> >  		panic_blink = no_blink;
> > -- 
> > 2.34.1
> > 
> 


WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: kexec@lists.infradead.org
Subject: [PATCH V3] panic: Move panic_print before kmsg dumpers
Date: Mon, 17 Jan 2022 14:13:15 +0800	[thread overview]
Message-ID: <20220117061315.GF2388@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220117033344.GA2523@MiWiFi-R3L-srv>

On 01/17/22 at 11:33am, Baoquan He wrote:
> On 01/14/22 at 03:30pm, Guilherme G. Piccoli wrote:
> ...... 
> >  .../admin-guide/kernel-parameters.txt         |  4 ++++
> >  kernel/panic.c                                | 22 ++++++++++++++-----
> >  2 files changed, 21 insertions(+), 5 deletions(-)
> > 
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> > index a069d8fe2fee..0f5cbe141bfd 100644
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -3727,6 +3727,10 @@
> >  			bit 4: print ftrace buffer
> >  			bit 5: print all printk messages in buffer
> >  			bit 6: print all CPUs backtrace (if available in the arch)
> > +			*Be aware* that this option may print a _lot_ of lines,
> > +			so there are risks of losing older messages in the log.
> > +			Use this option carefully, maybe worth to setup a
> > +			bigger log buffer with "log_buf_len" along with this.
> >  
> >  	panic_on_taint=	Bitmask for conditionally calling panic() in add_taint()
> >  			Format: <hex>[,nousertaint]
> > diff --git a/kernel/panic.c b/kernel/panic.c
> > index 41ecf9ab824a..4ae712665f75 100644
> > --- a/kernel/panic.c
> > +++ b/kernel/panic.c
> > @@ -148,10 +148,13 @@ void nmi_panic(struct pt_regs *regs, const char *msg)
> >  }
> >  EXPORT_SYMBOL(nmi_panic);
> >  
> > -static void panic_print_sys_info(void)
> > +static void panic_print_sys_info(bool after_kmsg_dumpers)
> >  {
> > -	if (panic_print & PANIC_PRINT_ALL_PRINTK_MSG)
> > -		console_flush_on_panic(CONSOLE_REPLAY_ALL);
> > +	if (after_kmsg_dumpers) {
> > +		if (panic_print & PANIC_PRINT_ALL_PRINTK_MSG)
> > +			console_flush_on_panic(CONSOLE_REPLAY_ALL);
> > +		return;
> > +	}
> >  
> >  	if (panic_print & PANIC_PRINT_ALL_CPU_BT)
> >  		trigger_all_cpu_backtrace();
> > @@ -249,7 +252,7 @@ void panic(const char *fmt, ...)
> >  	 * show some extra information on kernel log if it was set...
> >  	 */
> >  	if (kexec_crash_loaded())
> > -		panic_print_sys_info();
> > +		panic_print_sys_info(false);
> 
> Patch can'e be applied on the latest code of linus's tree, can you tell
> which branch your code are based on?

OK, this is based on linux-next, I will apply this patch on the
linux-next/master and have a look.

> 
> >  
> >  	/*
> >  	 * If we have crashed and we have a crash kernel loaded let it handle
> > @@ -283,6 +286,15 @@ void panic(const char *fmt, ...)
> >  	 */
> >  	atomic_notifier_call_chain(&panic_notifier_list, 0, buf);
> >  
> > +	/*
> > +	 * If kexec_crash_loaded() is true and we still reach this point,
> > +	 * kernel would double print the information from panic_print; so
> > +	 * let's guard against that possibility (it happens if kdump users
> > +	 * also set crash_kexec_post_notifiers in the command-line).
> > +	 */
> > +	if (!kexec_crash_loaded())
> > +		panic_print_sys_info(false);
> > +
> >  	kmsg_dump(KMSG_DUMP_PANIC);
> >  
> >  	/*
> > @@ -313,7 +325,7 @@ void panic(const char *fmt, ...)
> >  	debug_locks_off();
> >  	console_flush_on_panic(CONSOLE_FLUSH_PENDING);
> >  
> > -	panic_print_sys_info();
> > +	panic_print_sys_info(true);
> >  
> >  	if (!panic_blink)
> >  		panic_blink = no_blink;
> > -- 
> > 2.34.1
> > 
> 



  reply	other threads:[~2022-01-17  6:13 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 18:30 [PATCH V3] panic: Move panic_print before kmsg dumpers Guilherme G. Piccoli
2022-01-14 18:30 ` Guilherme G. Piccoli
2022-01-17  3:33 ` Baoquan He
2022-01-17  3:33   ` Baoquan He
2022-01-17  6:13   ` Baoquan He [this message]
2022-01-17  6:13     ` Baoquan He
2022-01-17 12:58     ` Guilherme G. Piccoli
2022-01-17 12:58       ` Guilherme G. Piccoli
2022-01-19  7:13 ` Baoquan He
2022-01-19  7:13   ` Baoquan He
2022-01-19 12:57   ` Guilherme G. Piccoli
2022-01-19 12:57     ` Guilherme G. Piccoli
2022-01-19 15:48   ` Petr Mladek
2022-01-19 15:48     ` Petr Mladek
2022-01-19 16:03     ` Guilherme G. Piccoli
2022-01-19 16:03       ` Guilherme G. Piccoli
2022-01-20  9:39       ` Petr Mladek
2022-01-20  9:39         ` Petr Mladek
2022-01-20 15:51         ` Guilherme G. Piccoli
2022-01-20 15:51           ` Guilherme G. Piccoli
2022-01-20  8:51     ` Baoquan He
2022-01-20  8:51       ` Baoquan He
2022-01-20 21:36       ` Guilherme G. Piccoli
2022-01-20 21:36         ` Guilherme G. Piccoli
2022-01-21  2:31         ` Baoquan He
2022-01-21  2:31           ` Baoquan He
2022-01-21 13:17           ` Guilherme G. Piccoli
2022-01-21 13:17             ` Guilherme G. Piccoli
2022-01-22 10:31             ` Baoquan He
2022-01-22 10:31               ` Baoquan He
2022-01-22 13:49               ` Guilherme G. Piccoli
2022-01-22 13:49                 ` Guilherme G. Piccoli
2022-01-26  3:29                 ` Baoquan He
2022-01-26  3:29                   ` Baoquan He
2022-01-21 15:00           ` Michael Kelley (LINUX)
2022-01-21 15:00             ` Michael Kelley
2022-01-22  4:33             ` Baoquan He
2022-01-22  4:33               ` Baoquan He
2022-01-24 16:57               ` Michael Kelley (LINUX)
2022-01-24 16:57                 ` Michael Kelley
2022-01-26 11:51                 ` Petr Mladek
2022-01-26 11:51                   ` Petr Mladek
2022-01-29  8:00                   ` Baoquan He
2022-01-29  8:00                     ` Baoquan He
2022-02-02 17:43                     ` Michael Kelley (LINUX)
2022-02-02 17:43                       ` Michael Kelley
2022-02-07  8:33                       ` Baoquan He
2022-02-07  8:33                         ` Baoquan He
2022-01-28  9:03                 ` Baoquan He
2022-01-28  9:03                   ` Baoquan He
2022-01-28 18:24                   ` Michael Kelley (LINUX)
2022-01-28 18:24                     ` Michael Kelley
2022-01-29  7:42                     ` Baoquan He
2022-01-29  7:42                       ` Baoquan He
2022-01-19 18:38 ` Petr Mladek
2022-01-19 18:38   ` Petr Mladek
2022-01-19 19:51   ` Guilherme G. Piccoli
2022-01-19 19:51     ` Guilherme G. Piccoli

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=20220117061315.GF2388@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=dyoung@redhat.com \
    --cc=feng.tang@intel.com \
    --cc=gpiccoli@igalia.com \
    --cc=john.ogness@linutronix.de \
    --cc=keescook@chromium.org \
    --cc=kernel@gpiccoli.net \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=tony.luck@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.