Re: how to trace files opening from a specific folder
Re: how to trace files opening from a specific folder
- Subject: Re: how to trace files opening from a specific folder
- From: "Quinn \"The Eskimo!\"" <email@hidden>
- Date: Tue, 1 Mar 2011 09:53:16 +0000
On 22 Feb 2011, at 15:27, Laurent Vinet wrote:
> Just a remark; I can't unload it...
>> sudo kextunload -v /tmp/tcplognke.kext
> (kernel) Kext com.apple.dts.kext.tcplognke did not stop (return code 0x5).
> (kernel) Kext com.apple.dts.kext.tcplognke can't unload - module stop returned 0xdc008017.
> Failed to unload com.apple.dts.kext.tcplognke - (libkern/kext) kext (kmod) start/stop routine failed.
The unload failed because com_apple_dts_kext_tcplognke_stop. Error code 5 in this context is KERN_FAILURE. If you look at the code, you'll see lots of reasons why it might return that error, the most likely being that the NKE is busy (that is, it's 'push' on top of an open TCP socket).
> Now, I need to test the same effect with KauthORama as the KE, and here it's not clear what I must do: redesign all the "Control Functions" like in tcplognke.c? and on the client side? Is the "socket filter" exist for KAUT architecture?
BSD-level KEXTs are pretty simplistic; getting these two things to work together is simply a question of mashing the code. The tricky part relates to synchronisation. Each KEXT has a set of entry points that, by and large, can be called by any thread. Moreover, some entry points are called on threads that you must not block, and some entry points are called on threads that, if you do block, run the risk of deadlocking the system. This trick is to understand and balance all of these requirements.
S+E
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden