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, 21 Sep 2009 13:37:18 +0800 From: Huang Ying <ying.huang@...el.com> To: Ingo Molnar <mingo@...e.hu> Cc: Borislav Petkov <borislav.petkov@....com>, Fr??d??ric Weisbecker <fweisbec@...il.com>, Li Zefan <lizf@...fujitsu.com>, Steven Rostedt <rostedt@...dmis.org>, "H. Peter Anvin" <hpa@...or.com>, Andi Kleen <ak@...ux.intel.com>, Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [BUGFIX -v7] x86, MCE: Fix bugs and issues of MCE log ring buffer Hi, Ingo, I think it is a interesting idea to replace the original MCE logging part implementation (MCE log ring buffer + /dev/mcelog misc device) with tracing infrastructure. The tracing infrastructure has definitely more features than original method, but it is more complex than original method too. The tracing infrastructure is good at tracing. But I think it may be too complex to be used as a (hardware) error processing mechanism. I think the error processing should be simple and relatively independent with other part of the kernel to avoid triggering more (hardware) error during error processing. What do you think about this? Even if we will reach consensus at some point to re-write MCE logging part totally. We still need to fix the bugs in original implementation before the new implementation being ready. Do you agree? Best Regards, Huang Ying -- 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