Re: KAUTH_FILEOP_EXEC & KAUTH_VNODE_EXECUTE freeze
site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Please file these as bugs against the sample code. <http://developer.apple.com/bugreporter/> 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. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... At 5:21 +0200 17/1/09, Liviu Andron wrote: 2) msleep related question: "Callers of this routine must be prepared for premature return, and check that the reason for sleeping has gone away" In the sample above, I can check if the reason for return is the user space answer, but how can I see if it is the timeout exit ? Is EWOULDBLOCK ok ? Yes. Also be prepared for EINTR and ERESTART, which both indicate that the thread was woken up in order to process a signal. 3) KauthORama sample has 2 problems - debug configuration panic on the line: "assert(*actionStrPtr != NULL)" - it doesn't know about KAUTH_FILEOP_DELETE This email sent to site_archiver@lists.apple.com
participants (1)
-
Quinn