linux-kernel - Re: [PATCH] sched: Panic on scheduling while atomic if kernel.panic_on

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 7 Jul 2016 17:25:00 -0300
From:	Daniel Bristot de Oliveira <bristot@...hat.com>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Christian Borntraeger <borntraeger@...ibm.com>,
	"Luis Claudio R. Goncalves" <lgoncalv@...hat.com>
Subject: Re: [PATCH] sched: Panic on scheduling while atomic if
 kernel.panic_on_warn is set

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