On (01/23/18 15:40), Sergey Senozhatsky wrote: > > Why do we even use irq_work for printk_safe? >
... perhaps because of
wq: pool->lock -> printk -> call_console_drivers -> printk -> vprintk_safe ->
wq: pool->lock
Which is a "many things have gone wrong" type of scenario. Maybe we
can workaround it somehow, hm. Tejun, can we have lockless WQ? ;)
-ss

