From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Gavin Hu <gavin.hu.2010@gmail.com>
Cc: Petr Mladek <pmladek@suse.com>,
linux-kernel@vger.kernel.org, Alex Elder <elder@linaro.org>,
"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>,
Joe Perches <joe@perches.com>,
Peter Hurley <peter@hurleysoftware.com>,
Tejun Heo <tj@kernel.org>,
cxie4@marvell.com, cldu@marvell.com, xjian@marvell.com,
fswu@marvell.com, Jan Kara <jack@suse.cz>
Subject: Re: printk: preempt_disable with long time resulting in softlockup/RCU stall issues
Date: Wed, 8 Jul 2015 19:04:02 +0200 [thread overview]
Message-ID: <20150708170402.GZ7021@wotan.suse.de> (raw)
In-Reply-To: <CABiPGEcBUiBfJYAREbiM0LDQM+iNeOzKmC_oCaL0Zh_humH23Q@mail.gmail.com>
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.
Luis
next prev parent reply other threads:[~2015-07-08 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABiPGEe=5tO5ffopExaHWV=fCb98vD5gHirt6vgXciA3hDrOfg@mail.gmail.com>
2015-07-08 8:13 ` printk: preempt_disable with long time resulting in softlockup/RCU stall issues Petr Mladek
[not found] ` <CABiPGEcBUiBfJYAREbiM0LDQM+iNeOzKmC_oCaL0Zh_humH23Q@mail.gmail.com>
2015-07-08 17:04 ` Luis R. Rodriguez [this message]
2015-07-08 17:35 ` Joe Perches
2015-07-08 18:00 ` Steven Rostedt
2015-07-09 7:56 ` Petr Mladek
2015-07-09 14:10 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150708170402.GZ7021@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=cldu@marvell.com \
--cc=cxie4@marvell.com \
--cc=elder@linaro.org \
--cc=fswu@marvell.com \
--cc=gavin.hu.2010@gmail.com \
--cc=jack@suse.cz \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=xjian@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox