| 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: Mon, 29 Mar 2010 12:55:14 +0200 From: Andi Kleen <andi@...stfloor.org> To: Hidetoshi Seto <seto.hidetoshi@...fujitsu.com> Cc: linux-kernel@...r.kernel.org, mingo@...e.hu, hpa@...or.com, tglx@...utronix.de Subject: Re: [PATCH] x86: mce: Xeon75xx specific interface to get corrected memory error information v2 Hidetoshi Seto <seto.hidetoshi@...fujitsu.com> writes: > I have some questions: Is it impossible to get the address > after polling handler have processed? e.g. Is it possible to > implement this module as mcelog's add-on that hooked & invoked > immediately after reading /dev/mcelog? I guess there are > some limitation/restriction to call pfa_command(). You need to be in ring 0. In theory you could do it later, but then you risk losing the address if there is another error. > Are there any alternative way to get the address? No. > Polling like edac_i7 doesn't help this? No. > > You pointed "This makes it impossible to do predictive failure > analysis", but I guess we could do rough-but-enough analysis that > requires coarse resolution like sockets. Or we should not expect The main predictive failure analysis interesting here is bad page offlining and for that you need an address. -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