Re: [PATCH] printk: make printk_safe_flush safe in NMI context by skipping flushing

2018-06-01 Thread Petr Mladek
Rostedt ; > > Hoeun Ryu ; linux-kernel@vger.kernel.org > > Subject: Re: [PATCH] printk: make printk_safe_flush safe in NMI context by > > skipping flushing > > > > On Tue 2018-05-29 21:13:15, Sergey Senozhatsky wrote: > > > On (05/29/18

RE: [PATCH] printk: make printk_safe_flush safe in NMI context by skipping flushing

2018-05-31 Thread Hoeun Ryu
> -Original Message- > From: Petr Mladek [mailto:pmla...@suse.com] > Sent: Wednesday, May 30, 2018 5:32 PM > To: Sergey Senozhatsky > Cc: Hoeun Ryu ; Sergey Senozhatsky > ; Steven Rostedt ; > Hoeun Ryu ; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] printk

RE: [PATCH] printk: make printk_safe_flush safe in NMI context by skipping flushing

2018-05-31 Thread Hoeun Ryu
; Cc: Hoeun Ryu ; Sergey Senozhatsky > ; Steven Rostedt ; > Hoeun Ryu ; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] printk: make printk_safe_flush safe in NMI context by > skipping flushing > > On Tue 2018-05-29 21:13:15, Sergey Senozhatsky wrote: > > On (05/29/

Re: [PATCH] printk: make printk_safe_flush safe in NMI context by skipping flushing

2018-05-30 Thread Petr Mladek
On Tue 2018-05-29 21:13:15, Sergey Senozhatsky wrote: > On (05/29/18 11:51), Hoeun Ryu wrote: > > Make printk_safe_flush() safe in NMI context. > > nmi_trigger_cpumask_backtrace() can be called in NMI context. For example > > the > > function is called in watchdog_overflow_callback() if the flag

RE: [PATCH] printk: make printk_safe_flush safe in NMI context by skipping flushing

2018-05-29 Thread Hoeun Ryu
Re: [PATCH] printk: make printk_safe_flush safe in NMI context by > skipping flushing > > On (05/29/18 11:51), Hoeun Ryu wrote: > > Make printk_safe_flush() safe in NMI context. > > nmi_trigger_cpumask_backtrace() can be called in NMI context. For > example the > > fun

Re: [PATCH] printk: make printk_safe_flush safe in NMI context by skipping flushing

2018-05-29 Thread Sergey Senozhatsky
On (05/29/18 11:51), Hoeun Ryu wrote: > Make printk_safe_flush() safe in NMI context. > nmi_trigger_cpumask_backtrace() can be called in NMI context. For example the > function is called in watchdog_overflow_callback() if the flag of hardlockup > backtrace (sysctl_hardlockup_all_cpu_backtrace) is

[PATCH] printk: make printk_safe_flush safe in NMI context by skipping flushing

2018-05-28 Thread Hoeun Ryu
From: Hoeun Ryu Make printk_safe_flush() safe in NMI context. nmi_trigger_cpumask_backtrace() can be called in NMI context. For example the function is called in watchdog_overflow_callback() if the flag of hardlockup backtrace (sysctl_hardlockup_all_cpu_backtrace) is true and watchdog_overflow_c

[PATCH] printk: make printk_safe_flush safe in NMI context

2018-05-28 Thread Hoeun Ryu
From: Hoeun Ryu Make printk_safe_flush() safe in NMI context. And printk_safe_flush_on_panic() is folded into this function. The prototype of printk_safe_flush() is changed to "void printk_safe_flush(bool panic)". nmi_trigger_cpumask_backtrace() can be called in NMI context. For example the f