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
| ||
|
Date: Tue, 03 Mar 2009 13:59:55 +1030 From: David Newall <davidn@...idnewall.com> To: linux-kernel@...r.kernel.org Subject: Re: Failover Kernel Tarkan Erimer wrote: > the point is not to make boot when crash occured. The idea is to take > control when a crash occured by backup kernel without any need to reboot. It sounds like you want everything to just continue running. I don't see how that can be done. All of those in-kernel tables and structures would need to be migrated, and it follows, because there was a crash, that any of them might have been corrupted. Worse, you want this to save you when you try running a new kernel which crashes, and being a new kernel, it follows that any of those structures could be different; it might not be possible to create equivalent structures for different kernel versions. If you're at all concerned at keeping the computer running, and I think that's your goal, then I think the best you can do is reset the hardware, boot an alternate kernel and restart applications as appropriate. -- 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