From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759249AbbGHRff (ORCPT ); Wed, 8 Jul 2015 13:35:35 -0400 Received: from smtprelay0222.hostedemail.com ([216.40.44.222]:57411 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758258AbbGHRfe (ORCPT ); Wed, 8 Jul 2015 13:35:34 -0400 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::::::::::::::::::::,RULES_HIT:41:355:379:541:599:973:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1539:1593:1594:1711:1730:1747:1777:1792:2393:2553:2559:2562:2828:3138:3139:3140:3141:3142:3352:3622:3865:3866:3867:3868:3872:3873:3874:4184:4250:4321:5007:6119:6261:6742:7903:10004:10400:10848:11232:11658:11914:12296:12517:12519:12740:13069:13095:13255:13311:13357:21060:21080,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0 X-HE-Tag: bit69_876a2505eb052 X-Filterd-Recvd-Size: 1978 Message-ID: <1436376929.2682.85.camel@perches.com> Subject: Re: printk: preempt_disable with long time resulting in softlockup/RCU stall issues From: Joe Perches To: "Luis R. Rodriguez" Cc: Gavin Hu , Petr Mladek , linux-kernel@vger.kernel.org, Alex Elder , "Steven Rostedt (Red Hat)" , Peter Hurley , Tejun Heo , cxie4@marvell.com, cldu@marvell.com, xjian@marvell.com, fswu@marvell.com, Jan Kara Date: Wed, 08 Jul 2015 10:35:29 -0700 In-Reply-To: <20150708170402.GZ7021@wotan.suse.de> References: <20150708081334.GJ32664@pathway.suse.cz> <20150708170402.GZ7021@wotan.suse.de> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.12.11-0ubuntu3 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2015-07-08 at 19:04 +0200, Luis R. Rodriguez wrote: > On Wed, Jul 08, 2015 at 05:08:35PM +0800, Gavin Hu wrote: > > Hi, > > > > Yes. We should disable the printk_limit feature when panic to avoid missing > > messages. > > Sounds like you have been looking into it and have a good idea of what you > want to do, why not try it and send some RFC patches ? > > While at it, then we could consider doing different things depending on the > message type. KERN_EMERG would disable preemption, whereas KERN_INFO may not be > so critical to require it. That might be a bit difficult to implement with complete correctness given KERN_EMERG use and continuation lines.