Re: [PATCH] Fix rq->lock vs logbuf_lock unlock race

[Peter Zijlstra]

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.

--
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/