Re: [GIT PULL] printk: Support for full dynticks mode

[Andrew Morton <akpm@linux-foundation.org>]

On Tue, 5 Feb 2013 02:37:54 +0100 Frederic Weisbecker <fweisbec@gmail.com> wrote:

> 2013/2/5 Andrew Morton <akpm@linux-foundation.org>:
> > On Tue,  5 Feb 2013 01:51:18 +0100
> > Frederic Weisbecker <fweisbec@gmail.com> wrote:
> >
> >>       printk: Wake up klogd using irq_work
> >
> > That seems reasonable.
> >
> > I'm wondering if we can now remove the printk_sched() special-case.
> > iirc, that was needed because wake_up(klogd) would deadlock when called
> > from sched internals.  But now that wakeup is punted to the timer tick,
> > perhaps this is now unnecessary?
> 
> I fear irq work doesn't change much the picture in this regard. Before
> irq work, printk() and printk_sched() were already relying on the tick
> (printk_tick()) to do the wake up on klogd clients. I guess that the
> deadlocks referenced by Peter were about printk() internals. May be
> logbuf_lock against some other scheduler lock?

I don't think so.  Conceptually printk() should be "inner" to the
scheduler and shouldn't call into sched things at all.  The (afaik
sole) exception to that was the klogd wakeup.

Traditionally the deadlock happened when calling printk() with
tasklist_lock (now q->lock) held.  printk() would call wake_up(klogd)
and wake_up() tries to take tasklist_lock and boom.  Moving the
wake_up() out to the tick "thread" fixed that.

Maybe there were other deadlock scenarios, dunno.  That knowledge
appears to be disappearing into the mists of time :(