linux-kernel - notify_page_fault

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <44D75ACE.76E4.0078.0@novell.com>
Date:	Mon, 07 Aug 2006 14:22:54 +0100
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	<anil.s.keshavamurthy@...el.com>, "Andrew Morton" <akpm@...l.org>,
	"Andreas Kleen" <ak@...e.de>
Cc:	<linux-kernel@...r.kernel.org>
Subject: notify_page_fault_chain

All,

I just noticed this addition to i386 and x86-64, conditionalized upon CONFIG_KPROBES. May I ask what the motivation for
this compatibility breaking change is? Only performance? 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.

Thanks for any clarification,
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/