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] [day] [month] [year] [list]
Date:	Thu, 10 Mar 2016 01:09:07 +0100
From:	Ralf Baechle <ralf@...ux-mips.org>
To:	Aaro Koskinen <aaro.koskinen@....fi>
Cc:	"James E.J. Bottomley" <jejb@...isc-linux.org>,
	Helge Deller <deller@....de>, linux-mips@...ux-mips.org,
	linux-parisc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] MIPS/PA-RISC: panic immediately when panic_on_oops

On Wed, Mar 09, 2016 at 10:08:41PM +0200, Aaro Koskinen wrote:

> MIPS and PA-RISC want to sleep 5 seconds before panicking when
> panic_on_oops is set, with no apparent reason. We should remove
> this feature, since some users may want their systems to fail as
> quickly as possible.
> 
> Users who want to delay reboot after panic can use PANIC_TIMEOUT.
> 
> Also, this change will unify the behaviour with other architectures.

I did a bit of dumpster diving, commit cea6a4ba8acfba6f59cc9ed71e0d05cb770b9d9c
("[PATCH] panic_on_oops: remove ssleep()") removed the 5 second delay
from ARM, i386, ia64, powerpc, x86_64 and xtensa on 2006-03-07.

The idea once upon a time probably was to keep the panic message on the
console long enough so somebody has _maybe_ a chance to read it.  Which
is a pretty weak solution.

  Ralf

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ