Messages in this thread | | | Subject | Re: [PATCH] Fix rq->lock vs logbuf_lock unlock race | From | Peter Zijlstra <> | Date | Wed, 20 Feb 2013 11:19:15 +0100 |
| |
On Wed, 2013-02-20 at 09:38 +0000, Bu, Yitian wrote: > > 2. from printk comment: "This is printk(). It can be called from any > context. > We want it to work. ". I suppose to use printk in any context.
Unfortunately that's not quite possible, rq->lock is really out of bounds. At one point I tried 'fixing' this but there's a whole bunch of nasty that's not going to go away.
I've since forgotten most of the details, but aside from logbuf problems there's a whole host of issues with the console drivers themselves as well.
If you really want to do this, use early_printk.
| |