Re: [RFC][PATCHv2 5/8] sysrq: switch to printk.emergency mode in unsafe places

2017-03-31 Thread Sergey Senozhatsky
Hello, On (03/31/17 17:37), Petr Mladek wrote: > On Wed 2017-03-29 18:25:08, Sergey Senozhatsky wrote: > > It's not always possible/safe to wake_up() printk kernel > > thread from sysrq (theoretically). Thus we better switch > > printk() to emergency mode in some of the sysrq handlers, > > which a

Re: [RFC][PATCHv2 5/8] sysrq: switch to printk.emergency mode in unsafe places

2017-03-31 Thread Petr Mladek
On Wed 2017-03-29 18:25:08, Sergey Senozhatsky wrote: > It's not always possible/safe to wake_up() printk kernel > thread from sysrq (theoretically). Thus we better switch > printk() to emergency mode in some of the sysrq handlers, > which allows us to immediately flush pending kernel message > to

[RFC][PATCHv2 5/8] sysrq: switch to printk.emergency mode in unsafe places

2017-03-29 Thread Sergey Senozhatsky
It's not always possible/safe to wake_up() printk kernel thread from sysrq (theoretically). Thus we better switch printk() to emergency mode in some of the sysrq handlers, which allows us to immediately flush pending kernel message to the console. This patch adds printk_emergency_begin/on sections