Messages in this thread | | | Subject | Re: [PATCH] Fix rq->lock vs logbuf_lock unlock race | From | Peter Zijlstra <> | Date | Wed, 20 Feb 2013 09:45:10 +0100 |
| |
On Mon, 2013-02-18 at 12:53 +0000, Bu, Yitian wrote: > This patch is for kernel V3.7.9 > > From 8796f4a2175a323aaa49ea8dd0fe68678dd5dccd Mon Sep 17 00:00:00 2001 > From: ybu <ybu@qti.qualcomm.com> > Date: Mon, 18 Feb 2013 19:52:01 +0800 > Subject: [PATCH] Fix rq->lock vs logbuf_lock unlock race > > fix up the fallout from commit 07354eb1a74d1 ("locking printk: > Annotate logbuf_lock as raw") > Release console_sem after unlocking the logbuf_lock avoids some lock > inversion troubles between logbuf_lock and rq->lock.
Please clarify how and where.. you're not actually supposed to use printk() while holding rq->lock.
| |