Re: [RFC][PATCH 0/6] Use printk_safe context for TTY and UART port locks
From: Linus Torvalds
Date: Tue Jun 19 2018 - 23:38:20 EST
On Wed, Jun 20, 2018 at 11:50 AM Sergey Senozhatsky
<sergey.senozhatsky.work@xxxxxxxxx> wrote:
>
> It's not UART on its own that immediately calls into printk(), that would
> be trivial to fix, it's all those subsystems that serial console driver
> can call into.
We already have the whole PRINTK_SAFE_CONTEXT_MASK model that only
adds it to a secondary buffer if you get recursion. Why isn't that
triggering? That's the whole point of it.
I absolutely do *not* want to see any crazy changes to tty drivers. No no no.
Linus