| 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
| ||
|
Message-ID: <20110328161622.100e3a51@lxorguk.ukuu.org.uk> Date: Mon, 28 Mar 2011 16:16:22 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Anithra P Janakiraman <anithra@...ux.vnet.ibm.com> Cc: linux-kernel@...r.kernel.org, dave@...ux.vnet.ibm.com, xiyou.wangcong@...il.com, sugaken.r3@...il.com, akpm@...ux-foundation.org, vatsa@...ux.vnet.ibm.com, ananth@...ibm.com Subject: Re: [RESEND] [PATCH] Softdog enhancement to optionally invoke panic instead of reboot on timer expiry On Mon, 28 Mar 2011 20:35:02 +0530 Anithra P Janakiraman <anithra@...ux.vnet.ibm.com> wrote: > Hi, > > The patch is needed for determining the reason for failure when a > softdog timeout occurs. We use softdog to watch for critical > application failures and at the minimum a snapshot of the system would > help to determine the cause. In such a scenario the application could > fail but there isn't a softlockup as such, hence the detect softlockup > feature does not help. The patch below adds a module parameter > soft_panic which when set to 1 causes softdog to invoke panic instead > of reboot when the softdog timer expires. By invoking panic we execute > kdump if it is configured and the vmcore generated by kdump should > provide atleast a minimal idea of the reason for failure. Looks sensible to me. Acked-by: Alan Cox <alan@...ux.intel.com> Alan -- 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/
Powered by blists - more mailing lists