Re: [PATCH 1/3] printk: Release console_sem after logbuf_lock

Ingo Molnar
2011-06-10T09:34:07Z

* Andrew Morton <akpm@linux-foundation.org> wrote:

> > Some notes:
>
> Stupid thing doesn't explain the magical locking though :( I'm
> 99.9% sure that putting an up() inside a spinlock_irq()ed region
> was deliberate.

My guess would be it's done so that pending irqs that have queued up
during our current printk-ing activities do not hit us with the
console still locked.

Thanks,

Ingo