From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Daniel Bristot de Oliveira <bristot@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Subject: Re: [RFC PATCH 0/2] sysctl: Panic on RCU stall and schedule while atomic
Date: Tue, 31 May 2016 21:27:24 +0200 [thread overview]
Message-ID: <574DE59C.1040904@de.ibm.com> (raw)
In-Reply-To: <cover.1464652607.git.bristot@redhat.com>
On 05/31/2016 09:07 PM, Daniel Bristot de Oliveira wrote:
> This patch series implements two kernel.panic_on_* like sysctl:
>
> kernel.panic_on_rcu_stall:
> panic() on RCU Stall detection.
>
> kernel.panic_on_sched_in_atomic:
> panic() on schedule while atomic detection.
>
> These sysctls are useful to capture a vmcore when is not possible
> to recompile the kernel to include the panic() call. For instance
> when supporting enterprise users.
>
> Daniel Bristot de Oliveira (2):
> rcu: sysctl: Panic on RCU Stall
> sched: sysctl: Panic on scheduling while atomic
>
> Documentation/sysctl/kernel.txt | 25 +++++++++++++++++++++++++
> include/linux/kernel.h | 2 ++
> kernel/rcu/tree.c | 8 ++++++++
> kernel/sched/core.c | 7 +++++++
> kernel/sysctl.c | 20 ++++++++++++++++++++
> 5 files changed, 62 insertions(+)
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
for both changes. I too often had to add manual panics in a test
kernel and reproduce an issue. This will allow to take a (k)dump at a point
in time where the data structures might still explain what happened.
As this is an opt-in nobody, this should not cause any trouble for
people that do not want to take dumps.
Christian
prev parent reply other threads:[~2016-05-31 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 19:07 [RFC PATCH 0/2] sysctl: Panic on RCU stall and schedule while atomic Daniel Bristot de Oliveira
2016-05-31 19:07 ` [RFC PATCH 1/2] rcu: sysctl: Panic on RCU Stall Daniel Bristot de Oliveira
2016-05-31 19:18 ` Josh Triplett
2016-05-31 19:23 ` Josh Triplett
2016-05-31 22:49 ` Daniel Bristot de Oliveira
2016-06-01 2:34 ` Paul E. McKenney
2016-05-31 19:07 ` [RFC PATCH 2/2] sched: sysctl: Panic on scheduling while atomic Daniel Bristot de Oliveira
2016-05-31 19:20 ` Josh Triplett
2016-06-01 9:45 ` Peter Zijlstra
2016-06-01 13:37 ` Daniel Bristot de Oliveira
2016-05-31 19:27 ` Christian Borntraeger [this message]
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=574DE59C.1040904@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=acme@kernel.org \
--cc=bristot@redhat.com \
--cc=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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