From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753694AbcCANQj (ORCPT ); Tue, 1 Mar 2016 08:16:39 -0500 Received: from mail-pf0-f179.google.com ([209.85.192.179]:33228 "EHLO mail-pf0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751976AbcCANQi (ORCPT ); Tue, 1 Mar 2016 08:16:38 -0500 Date: Tue, 1 Mar 2016 22:14:34 +0900 From: Sergey Senozhatsky To: Petr Mladek Cc: Sergey Senozhatsky , Andrew Morton , Jan Kara , Peter Zijlstra , Steven Rostedt , Ingo Molnar , linux-kernel@vger.kernel.org, Sergey Senozhatsky Subject: Re: [PATCH] printk/nmi: restore printk_func in nmi_panic Message-ID: <20160301131434.GA518@swordfish> References: <1456457840-1059-1-git-send-email-sergey.senozhatsky@gmail.com> <20160226145717.GZ12548@pathway.suse.cz> <20160227021944.GA1621@swordfish> <20160229103141.GL3305@pathway.suse.cz> <20160229111937.GA356@swordfish> <20160301092426.GA2968@swordfish> <20160301110528.GO3305@pathway.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160301110528.GO3305@pathway.suse.cz> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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