linux-kernel - Re: [PATCH] Introduce softpanic

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:	Fri, 25 Jan 2008 16:22:51 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Andi Kleen <andi@...stfloor.org>
cc:	Bodo Eggert <7eggert@....de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Introduce softpanic


On Jan 25 2008 16:01, Andi Kleen wrote:
>Bodo Eggert <7eggert@....de> writes:
>
>> Enabling this option changes a hard panic on boot errors to a
>> soft panic, which does not stop the system completely.
>> You can still scroll the screen and read the messages.
>
>I don't think it's a good idea to keep the network running in the
>soft panic. A lot of people have set ups that use ping was a watchdog
>and with nfsroot/ip=dhcp ping does work quite well before
>mounting root and then the watchdog might not pick up the 
>soft panic.

If the machine goes oops and softlocks (e.g. bug in root filesystem,
lock held but not released, box essentially dead), ping also still
works even though you'd probably want to trigger the watchdog too.

>Using a polled keyboard driver after panic seems to be the better
>option to me, but if you want softpanic you should probably
>at least add a suitable panic notifier to the network stack 
>to shut it all down.

or that.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/