[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160301131434.GA518@swordfish>
Date: Tue, 1 Mar 2016 22:14:34 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To: Petr Mladek <pmladek@...e.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jan Kara <jack@...e.cz>, Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Subject: Re: [PATCH] printk/nmi: restore printk_func in nmi_panic
On (03/01/16 12:05), Petr Mladek wrote:
[..]
> > > yes, well, that's true for panic() in general.
> >
> > Petr, what do you think of this (added PRINTK_NMI_FLUSH_ON_PANIC)?
> >
> > 1) zap_locks() in console_flush_on_panic()
> > 2) add PRINTK_NMI_FLUSH_ON_PANIC symbols
> > 3) add printk_nmi_flush_on_panic()
>
> This is definitely better than nothing. Well, it seems that
> the printk/NMI patches that motivated this patch will be
> removed for a while, see
> http://thread.gmane.org/gmane.linux.ports.arm.kernel/482845/focus=483002
>
Oh, thanks a lot for the link! wasn't aware of it.
> I want to play with the panic handling a bit more and make it better
> working out of box. It might be enough to put the messages into
> the rind buffer when crashdump is going to be produced. Also
> there is still the idea about using the lock-less early console.
> I think that the solution from this patch might be the last
> fallback.
>
> Thanks a lot for proposals,
OK, good to know that.
-ss
Powered by blists - more mailing lists