Re: [RFC PATCH v1 00/25] printk: new implementation
From: Sergey Senozhatsky
Date: Tue Mar 12 2019 - 22:15:41 EST
On (03/12/19 16:15), John Ogness wrote:
> > I suggest the following way forward (separate patchsets):
> > 1. Replace log buffer (least controversial thing)
> Yes. I will post a series that only implements the ringbuffer using your
> simplified API. That will be enough to remove printk_safe and actually
> does most of the work of updating devkmsg, kmsg_dump, and syslog.
This may _not_ be enough to remove printk_safe. One of the reasons
printk_safe "condom" came into existence was console_sem (which
is a bit too important to ignore it):
raw_spin_lock_irqsave(&sem->lock, flags) << deadlock
Back then we were looking at
deadlock report from LG, if I'm not mistaken.