Re: [PATCH printk v1 10/13] printk: add kthread console printers

[Sergey Senozhatsky]

On (22/02/08 15:53), Petr Mladek wrote:
> My mine concern is that the kthread_worker API still uses an internal
> lock. And it is yet another layer that might be hard to debug when
> printk() does not work.

Isn't this also true for kthreads? Looks like we add "couple of spin_locks"
to the picture - rq, etc. - one way of the other.