Re: Regression in fd5f7cde1b85 ("printk: Never set console_may_schedule in console_trylock()")

2019-09-17 Thread Sergey Senozhatsky
On (09/17/19 16:10), Uwe Kleine-König wrote: > Hello, > > Today it saw sysrq on an UART driven by drivers/tty/serial/imx.c report > a lockdep issue. Bisecting pointed to > > fd5f7cde1b85 ("printk: Never set console_may_schedule in > console_trylock()") Hmmm... I don't see how this patch

Regression in fd5f7cde1b85 ("printk: Never set console_may_schedule in console_trylock()")

2019-09-17 Thread Uwe Kleine-König
Hello, Today it saw sysrq on an UART driven by drivers/tty/serial/imx.c report a lockdep issue. Bisecting pointed to fd5f7cde1b85 ("printk: Never set console_may_schedule in console_trylock()") When I type t I get: [ 87.940104] sysrq: SysRq : This sysrq operation is disabled. [