| 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, 07 Aug 2006 15:50:40 +0100 From: "Jan Beulich" <jbeulich@...ell.com> To: "Andi Kleen" <ak@...e.de> Cc: <anil.s.keshavamurthy@...el.com>, "Andrew Morton" <akpm@...l.org>, <linux-kernel@...r.kernel.org> Subject: Re: notify_page_fault_chain >> I consider it already questionable to split out a specific >> fault from the general die notification (previous users of the functionality all of the sudden won't get notifications >> for one of the most crucial faults anymore), but entirely hiding the functionality (unavailable without CONFIG_KPROBES, >> and even with it not getting exported) is really odd. > >You want to use it for your debugger? Yes, in its "light" form (i.e. without exception handling framework changes) it has to rely on this infrastructure. Jan - 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