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

[Ingo Molnar]

* Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/