panic: Avoid the extra noise dmesg
Subsystems (2)
PATCH v6 1/1 panic: Avoid the extra noise dmesg
When kernel panic happens, it will first print the panic call stack, then the ending msg like:
[ 35.743249] ---[ end Kernel panic - not syncing: Fatal exception [ 35.749975] ------------[ cut here ]------------
The above message are very useful for debugging.
But if system is configured to not reboot on panic, say the "panic_timeout" parameter equals 0, it will likely print out many noisy message like WARN() call stack for each and every CPU except the panic one, messages like below:
WARNING: CPU: 1 PID: 280 at kernel/sched/core.c:1198 set_task_cpu+0x183/0x190 Call Trace: <IRQ> try_to_wake_up default_wake_function autoremove_wake_function __wake_up_common __wake_up_common_lock __wake_up wake_up_klogd_work_func irq_work_run_list irq_work_tick update_process_times tick_sched_timer __hrtimer_run_queues hrtimer_interrupt smp_apic_timer_interrupt apic_timer_interrupt
For people working in console mode, the screen will first show the panic call stack, but immediately overridden by these noisy extra messages, which makes debugging much more difficult, as the original context gets lost on screen.
Also these noisy messages will confuse some users, as I have seen many bug reporters posted the noisy message into bugzilla, instead of the real panic call stack and context.
Adding a flag "suppress_printk" which gets set in panic() to avoid those noisy messages, without changing current kernel behavior that both panic blinking and sysrq magic key can work as is, suggested by Petr Mladek.
To verify this, make sure kernel is not configured to reboot on panic and in console
# echo c > /proc/sysrq-trigger to see if console only prints out the panic call stack.
---
Change log:
v6:
- change the flag name from "panic_suppress_printk" to suppress_printk, as suggested by Andrew Morton
v5:
- use a flag to notify printk not to print unimportant messages, while keeping panic blinking and sysrq working, as suggested by Petr Mladek
v4:
- make the local_irq_enable conditional and default off to cover possible use of interrupt/scheduling, as mentioned by Sergey and Petr
v3:
- Make the change log clearer as suggested by Andrew Morton
v2:
- Move the solution from hacking arch/scheduler code back to panic.c
drivers/tty/sysrq.c | 6 ++++++ include/linux/printk.h | 2 ++ kernel/panic.c | 3 +++ kernel/printk/printk.c | 10 ++++++++++ 4 files changed, 21 insertions(+)
drivers/tty/sysrq.c +6 -0
@@ -527,8 +527,12 @@ void __handle_sysrq(int key, bool check_mask) {struct sysrq_key_op *op_p;int orig_log_level; +int orig_suppress_printk;int i; + orig_suppress_printk = suppress_printk; + suppress_printk =0 ; +rcu_sysrq_start ();rcu_read_lock ();/*
@@ -574,6 +578,8 @@ void __handle_sysrq(int key, bool check_mask) }rcu_read_unlock ();rcu_sysrq_end (); + + suppress_printk = orig_suppress_printk; }void handle_sysrq (int key)
include/linux/printk.h +2 -0
@@ -83,6 +83,8 @@ static inline void console_verbose(void)extern char devkmsg_log_str[];struct ctl_table ; +extern int suppress_printk; +struct va_format {const char *fmt;va_list *va;
kernel/panic.c +3 -0
@@ -326,6 +326,9 @@ void panic(const char *fmt, ...) }#endif pr_emerg ("---[ end Kernel panic - not syncing: %s ]---\n" , buf); + +/* Do not scroll important messages printed above */ + suppress_printk =1 ;local_irq_enable ();for (i =0 ; ; i +=PANIC_TIMER_STEP ) {touch_softlockup_watchdog ();
kernel/printk/printk.c +10 -0
@@ -85,6 +85,12 @@ static DEFINE_SEMAPHORE(console_sem);struct console *console_drivers;EXPORT_SYMBOL_GPL (console_drivers); +/* +* System may need to suppress printk message under certain +* circumstances, like after kernel panic happens. +*/ +int __read_mostly suppress_printk; +#ifdef CONFIG_LOCKDEP static struct lockdep_map console_lock_dep_map = { .name = "console_lock"
@@ -1899,6 +1905,10 @@ asmlinkage int vprintk_emit(int facility, int level,unsigned long flags;u64 curr_log_seq; +/* Suppress unimportant messages after panic happens */ +if (unlikely (suppress_printk)) +return 0 ; +if (level ==LOGLEVEL_SCHED ) { level =LOGLEVEL_DEFAULT ; in_sched = true;
Signature · 1 line
2.7.4
Quoted 45 lines · Feng Tang
When kernel panic happens, it will first print the panic call stack, then the ending msg like:
[ 35.743249] ---[ end Kernel panic - not syncing: Fatal exception [ 35.749975] ------------[ cut here ]------------The above message are very useful for debugging.
But if system is configured to not reboot on panic, say the "
panic_timeout" parameter equals 0, it will likely print out many noisy message likeWARN()call stack for each and every CPU except the panic one, messages like below:WARNING: CPU: 1 PID: 280 at kernel/sched/core.c:1198 set_task_cpu+0x183/0x190 Call Trace: <IRQ> try_to_wake_up default_wake_function autoremove_wake_function __wake_up_common __wake_up_common_lock __wake_up wake_up_klogd_work_func irq_work_run_list irq_work_tick update_process_times tick_sched_timer __hrtimer_run_queues hrtimer_interrupt smp_apic_timer_interrupt apic_timer_interruptFor people working in console mode, the screen will first show the panic call stack, but immediately overridden by these noisy extra messages, which makes debugging much more difficult, as the original context gets lost on screen.
Also these noisy messages will confuse some users, as I have seen many bug reporters posted the noisy message into bugzilla, instead of the real panic call stack and context.
Adding a flag "
suppress_printk" which gets set inpanic()to avoid those noisy messages, without changing current kernel behavior that both panic blinking and sysrq magic key can work as is, suggested by Petr Mladek.
Quoted 7 lines
To verify this, make sure kernel is not configured to reboot on panic and in console
# echo c > /proc/sysrq-trigger to see if console only prints out the panic call stack.Suggested-by Petr Mladek <[email protected]>Signed-off-by Feng Tang <[email protected]>
The patch looks fine to me:
Best Regards,
Petr
Quoted 41 lines · On Fri, 1 Mar 2019 16:49:46 +0800 Feng Tang <[email protected]> wrote:
When kernel panic happens, it will first print the panic call stack, then the ending msg like:
[ 35.743249] ---[ end Kernel panic - not syncing: Fatal exception [ 35.749975] ------------[ cut here ]------------The above message are very useful for debugging.
But if system is configured to not reboot on panic, say the "
panic_timeout" parameter equals 0, it will likely print out many noisy message likeWARN()call stack for each and every CPU except the panic one, messages like below:WARNING: CPU: 1 PID: 280 at kernel/sched/core.c:1198 set_task_cpu+0x183/0x190 Call Trace: <IRQ> try_to_wake_up default_wake_function autoremove_wake_function __wake_up_common __wake_up_common_lock __wake_up wake_up_klogd_work_func irq_work_run_list irq_work_tick update_process_times tick_sched_timer __hrtimer_run_queues hrtimer_interrupt smp_apic_timer_interrupt apic_timer_interruptFor people working in console mode, the screen will first show the panic call stack, but immediately overridden by these noisy extra messages, which makes debugging much more difficult, as the original context gets lost on screen.
Also these noisy messages will confuse some users, as I have seen many bug reporters posted the noisy message into bugzilla, instead of the real panic call stack and context.
Quoted 9 lines
Adding a flag "
suppress_printk" which gets set inpanic()to avoid those noisy messages, without changing current kernel behavior that both panic blinking and sysrq magic key can work as is, suggested by Petr Mladek.To verify this, make sure kernel is not configured to reboot on panic and in console
# echo c > /proc/sysrq-trigger to see if console only prints out the panic call stack.
Looks good to me.
Andrew, you want to take this patch?
-- Steve
Quoted 124 lines
Suggested-by Petr Mladek <[email protected]>Signed-off-by Feng Tang <[email protected]>Cc Thomas Gleixner <[email protected]>Cc Kees Cook <[email protected]>Cc Borislav Petkov <[email protected]>Cc Sergey Senozhatsky <[email protected]>Cc Petr Mladek <[email protected]>Cc Steven Rostedt <[email protected]>Cc Andi Kleen <[email protected]>Cc Peter Zijlstra <[email protected]>Cc Greg Kroah-Hartman <[email protected]>Cc Jiri Slaby <[email protected]>Cc Sasha Levin <[email protected]>---
Change log:v6:
- change the flag name from "panic_suppress_printk" tosuppress_printk, as suggested by Andrew Mortonv5:
- use a flag to notify printk not to print unimportant messages, while keeping panic blinking and sysrq working, as suggested by Petr Mladekv4:
- make thelocal_irq_enableconditional and default off to cover possible use of interrupt/scheduling, as mentioned by Sergey and Petrv3:
- Make the change log clearer as suggested by Andrew Mortonv2:
- Move the solution from hackingarch/schedulercode back topanic.cdrivers/tty/sysrq.c | 6 ++++++ include/linux/printk.h | 2 ++ kernel/panic.c | 3 +++ kernel/printk/printk.c | 10 ++++++++++ 4 files changed, 21 insertions(+)drivers/tty/sysrq.c +6
-0@@ -527,8 +527,12 @@ void __handle_sysrq(int key, bool check_mask) {struct sysrq_key_op *op_p;int orig_log_level; +int orig_suppress_printk;int i; + orig_suppress_printk = suppress_printk; + suppress_printk =0 ; +rcu_sysrq_start ();rcu_read_lock ();/* @@ -574,6 +578,8 @@ void __handle_sysrq(int key, bool check_mask) }rcu_read_unlock ();rcu_sysrq_end (); + + suppress_printk = orig_suppress_printk; }void handle_sysrq (int key)include/linux/printk.h +2
-0@@ -83,6 +83,8 @@ static inline void console_verbose(void)extern char devkmsg_log_str[];struct ctl_table ; +extern int suppress_printk; +struct va_format {const char *fmt;va_list *va;kernel/panic.c +3
-0@@ -326,6 +326,9 @@ void panic(const char *fmt, ...) }#endif pr_emerg ("---[ end Kernel panic - not syncing: %s ]---\n" , buf); + +/* Do not scroll important messages printed above */ + suppress_printk =1 ;local_irq_enable ();for (i =0 ; ; i +=PANIC_TIMER_STEP ) {touch_softlockup_watchdog ();kernel/printk/printk.c +10
-0@@ -85,6 +85,12 @@ static DEFINE_SEMAPHORE(console_sem);struct console *console_drivers;EXPORT_SYMBOL_GPL (console_drivers); +/* +* System may need to suppress printk message under certain +* circumstances, like after kernel panic happens. +*/ +int __read_mostly suppress_printk; +#ifdef CONFIG_LOCKDEP static struct lockdep_map console_lock_dep_map = { .name = "console_lock"@@ -1899,6 +1905,10 @@ asmlinkage int vprintk_emit(int facility, int level,unsigned long flags;u64 curr_log_seq; +/* Suppress unimportant messages after panic happens */ +if (unlikely (suppress_printk)) +return 0 ; +if (level ==LOGLEVEL_SCHED ) { level =LOGLEVEL_DEFAULT ; in_sched = true;
Quoted 5 lines · On Fri, 1 Mar 2019 16:57:52 -0500 Steven Rostedt <[email protected]> wrote:
Looks good to me.
Andrew, you want to take this patch?
Yup.
Quoted 12 lines · Feng Tang
When kernel panic happens, it will first print the panic call stack, then the ending msg like:
[ 35.743249] ---[ end Kernel panic - not syncing: Fatal exception [ 35.749975] ------------[ cut here ]------------The above message are very useful for debugging.
But if system is configured to not reboot on panic, say the "
panic_timeout" parameter equals 0, it will likely print out many noisy message likeWARN()call stack for each and every CPU except the panic one, messages like below:
[..]
-ss