| 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: <87wscxdyyf.fsf@basil.nowhere.org> Date: Thu, 15 Jan 2009 04:34:32 +0100 From: Andi Kleen <andi@...stfloor.org> To: "Jan Beulich" <jbeulich@...ell.com> Cc: <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] conditionalize call from panic() to smp_send_stop() "Jan Beulich" <jbeulich@...ell.com> writes: > ... avoiding nested warnings and/or oopses as much as possible (namely > durin early boot). Better would be to fix smp_send_stop than to work around it for this very limited case. I've been running into this with machine checks too. The new fancy smp_call_function() that is there now just doesn't work in any unusual situation like early boot or fatal exceptions, My thinking was to use a separate vector, or possible just the NMI. -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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