commit 4f2a8d3cf5e0486fd547633fa86c5d130ae98cad
author Peter Zijlstra <peterz@infradead.org> Wed Jun 22 11:20:09 2011 +0200
committer Ingo Molnar <mingo@elte.hu> Wed Jun 22 11:39:34 2011 +0200
tree 4f60a635565fd63473e5c23f45745b3b502a1d52
parent 0b5e1c5255e7ee8670e077e8224e5c2281229a5b

printk: Fix console_sem vs logbuf_lock unlock race

Fix up the fallout from commit 0b5e1c5255 ("printk: Release
console_sem after logbuf_lock").

The reason for unlocking the console_sem under the logbuf_lock
is that a concurrent printk() might fill up the buffer but fail
to acquire the console sem, resulting in a missed write to the
console until a subsequent console_sem acquire/release cycle.

Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: efault@gmx.de
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Link: http://lkml.kernel.org/r/1308734409.1022.14.camel@twins
Signed-off-by: Ingo Molnar <mingo@elte.hu>