On (01/22/18 19:28), Sergey Senozhatsky wrote: > On (01/22/18 17:56), Sergey Senozhatsky wrote: > [..] > > Assume the following, > > But more importantly we are missing another huge thing - console_unlock().
IOW, not every console_unlock() is from vprintk_emit(). We can have console_trylock() -> console_unlock() being from non-preemptible context, etc. And then irq work to flush printk_safe -> printk_deferred all the time. -ss