| 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: <47D6C0A8.6010504@nortel.com> Date: Tue, 11 Mar 2008 11:26:00 -0600 From: "Chris Friesen" <cfriesen@...tel.com> To: Daniel Phillips <phillips@...nq.net> CC: Lars Marowsky-Bree <lmb@...e.de>, Alan Cox <alan@...rguk.ukuu.org.uk>, Grzegorz Kulewski <kangur@...com.net>, linux-kernel@...r.kernel.org Subject: Re: [ANNOUNCE] Ramback: faster than a speeding bullet Daniel Phillips wrote: > On Tuesday 11 March 2008 04:23, Lars Marowsky-Bree wrote: > >>If I always assume a reliable shutdown - UPS protected, no crashes, etc >>- you're right, but at least my real world has other failure scenarios >>as well. In fact, the most common reason for unorderly shutdowns are >>kernel crashes, not power failures in my experience. > > > What are you doing to your kernel? <snip> > Honestly, I have never seen a machine running > Linux 2.6 crash due to a software flaw, except when I caused it > myself. I suspect the Linux kernel has a better MTBF than a hard > disk. I have experienced many 2.6 crashes due to software flaws. Hung processes leading to watchdog timeouts, bad kernel pointers, kernel deadlock, etc. When designing for reliable embedded systems it's not enough to handwave away the possibility of software flaws. Chris -- 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