From: "H. Peter Anvin" <hpa@zytor.com>
To: Prarit Bhargava <prarit@redhat.com>, linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Andi Kleen <ak@linux.intel.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Fabian Frederick <fabf@skynet.be>,
vgoyal@redhat.com, isimatu.yasuaki@jp.fujitsu.com,
jbaron@akamai.com, linux-doc@vger.kernel.org,
kexec@lists.infradead.org, linux-api@vger.kernel.org
Subject: Re: [PATCH] kernel, add panic_on_warn
Date: Thu, 30 Oct 2014 10:24:19 -0700 [thread overview]
Message-ID: <54527443.6030007@zytor.com> (raw)
In-Reply-To: <1414688627-5298-1-git-send-email-prarit@redhat.com>
On 10/30/2014 10:03 AM, Prarit Bhargava wrote:
> There have been several times where I have had to rebuild a kernel to
> cause a panic when hitting a WARN() in the code in order to get a crash
> dump from a system. Sometimes this is easy to do, other times (such as
> in the case of a remote admin) it is not trivial to send new images to the
> user.
>
> A much easier method would be a switch to change the WARN() over to a
> panic. This makes debugging easier in that I can now test the actual
> image the WARN() was seen on and I do not have to engage in remote
> debugging.
>
> This patch adds a panic_on_warn kernel parameter and
> /proc/sys/kernel/panic_on_warn calls panic() in the warn_slowpath_common()
> path. The function will still print out the location of the warning.
>
> An example of the panic_on_warn output:
>
> The first line below is from the WARN_ON() to output the WARN_ON()'s location.
> After that the panic() output is displayed.
>
There is another very valid use for this: many operators would rather a
machine shuts down than being potentially compromised either
functionally or security-wise.
-hpa
next prev parent reply other threads:[~2014-10-30 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 17:03 [PATCH] kernel, add panic_on_warn Prarit Bhargava
2014-10-30 17:24 ` H. Peter Anvin [this message]
2014-10-31 1:58 ` Hedi Berriche
2014-11-03 13:32 ` Prarit Bhargava
2014-11-03 15:18 ` Vivek Goyal
-- strict thread matches above, loose matches on Subject: below --
2014-11-04 15:41 Prarit Bhargava
2014-11-05 4:27 ` WANG Chao
2014-11-05 4:55 ` Yasuaki Ishimatsu
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=54527443.6030007@zytor.com \
--to=hpa@zytor.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=fabf@skynet.be \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jbaron@akamai.com \
--cc=kexec@lists.infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=prarit@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=vgoyal@redhat.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