Thread (24 messages) 24 messages, 7 authors, 2018-06-28

Re: [RFC][PATCH 0/6] Use printk_safe context for TTY and UART port locks

From: Alan Cox <hidden>
Date: 2018-06-22 16:23:37
Also in: lkml

On Wed, 20 Jun 2018 11:44:13 +0900
Linus Torvalds [off-list ref] wrote:
On Wed, Jun 20, 2018 at 11:34 AM Steven Rostedt [off-list ref] wrote:
quoted
Perhaps we should do an audit of the console drivers and remove all
printk, pr_* , WARN*, BUG* from them.  
Only the actual _printing_ parts.
No because they are normally rather useful because that port isn't the
console. If you trylock it as I suggested then at least you'd just drop
the recursive cases and get messages otherwise.

Really that's all that you need - log the message to whichever console
targets you can currently safely do so. If it's none well there was
always the proposed morse code keyboard light driver 8)

Alan
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help