Re: [PATCH v2] printk: Use the main logbuf in NMI when logbuf_lock is available
From: Sergey Senozhatsky
Date: Sat May 20 2017 - 05:05:37 EST
On (05/19/17 15:02), Petr Mladek wrote:
> > [..]
> > > the problem is that
> > >
> > > `PRINTK_NMI_CONTEXT_MASK || PRINTK_NMI_DEFERRED_CONTEXT_MASK' is 0x01
> > d'oh... forgot to copy-paste this...
> Grrr, thanks a lot for chasing this down and I am sorry for the troubles.
no worries :)
> I have rebased both for-4.13 and for-next branches in printk.git
> with this fix. I wanted to get rid of this bug in linux-next
> ASAP. Please, let me know if you would prefer to handle
> this another way in the future.
we are cool ;) thanks.