linux-kernel - Re: Need help with register_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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 19 Nov 2007 00:29:46 -0500
From:	Pavel Roskin <proski@....org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Need help with register_page_fault_notifier() replacement in
	2.6.24

Quoting Arjan van de Ven <arjan@...radead.org>:

> if it's just for a custom case (as it sounds like).. a simple small
> change to the pagefault handler sounds like the easiest thing to do...
> (eg just a direct function call to what would have been your notifier)

Thanks!  Actually, the idea is to make it easy many people to run the  
trace without having them to patch or downgrade their kernels.  Also,  
it would be convenient for ath5k developers to run (and perhaps  
improve) the trace on the current development kernel.

Also, the code was lifted from some nvidia debugging tool, so the  
improved code could be contributed back there.

I guess if there is no simple answer, I'll have to try a few crazy  
ideas.  If nothing works, the fault handler chain could be reinstated,  
perhaps as a separate configuration option.

-- 
Regards,
Pavel Roskin
-
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/