Re: [PATCH] sched: Panic on scheduling while atomic if kernel.panic_on_warn is set

From	Daniel Bristot de Oliveira <bristot@redhat.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH] sched: Panic on scheduling while atomic if kernel.panic_on_warn is set
Date	2016-07-07 22:30 +0200
Message-ID	<rSo5P-3n4-1@gated-at.bofh.it> (permalink)
References	<rG3Jv-7Qb-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 06/03/2016 05:10 PM, Daniel Bristot de Oliveira wrote:
> Currently, a schedule while atomic error prints the stack trace to the
> kernel log and the system continue running.
> 
> Although it is possible to collect the kernel log messages and analyze
> it, often more information are needed. Furthermore, keep the system
> running is not always the best choice. For example, when the preempt
> count underflows the system will not stop to complain about scheduling
> while atomic, so the kernel log can wrap around overwriting the first
> stack trace, tuning the analysis even more challenging.
> 
> This patch uses the kernel.panic_on_warn sysctl to help out on these
> more complex situations.
> 
> When kernel.panic_on_warn is set to 1, the kernel will panic() in the
> schedule while atomic detection.
> 
> The default value of the sysctl is 0, maintaining the current behavior.

A gentle ping...

Thoughts about this patch? or, should I resend the patch that implements
a specific sysctl to panic on scheduling while atomic?

Thanks in advance,
-- Daniel

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [PATCH] sched: Panic on scheduling while atomic if  kernel.panic_on_warn is set Daniel Bristot de Oliveira <bristot@redhat.com> - 2016-07-07 22:30 +0200

csiph-web