printk: Fix rq->lock vs logbuf_lock unlock lock inversion
authorBu, Yitian <ybu@qti.qualcomm.com>
Mon, 18 Feb 2013 12:53:37 +0000 (12:53 +0000)
committerThomas Gleixner <tglx@linutronix.de>
Mon, 18 Feb 2013 14:05:57 +0000 (15:05 +0100)
commitdbda92d16f8655044e082930e4e9d244b87fde77
treeb8e10565d24b46d953413d2d6caa612608dfb95f
parent211b0cdc7dc574e5e756bdf1cc2f4a16b7f6e07e
printk: Fix rq->lock vs logbuf_lock unlock lock inversion

commit 07354eb1a74d1 ("locking printk: Annotate logbuf_lock as raw")
reintroduced a lock inversion problem which was fixed in commit
0b5e1c5255 ("printk: Release console_sem after logbuf_lock"). This
happened probably when fixing up patch rejects.

Restore the ordering and unlock logbuf_lock before releasing
console_sem.

Signed-off-by: ybu <ybu@qti.qualcomm.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: stable@vger.kernel.org
Link: http://lkml.kernel.org/r/E807E903FE6CBE4D95E420FBFCC273B827413C@nasanexd01h.na.qualcomm.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
kernel/printk.c