Re: KAUTH_FILEOP_EXEC & KAUTH_VNODE_EXECUTE freeze
Re: KAUTH_FILEOP_EXEC & KAUTH_VNODE_EXECUTE freeze
- Subject: Re: KAUTH_FILEOP_EXEC & KAUTH_VNODE_EXECUTE freeze
- From: Terry Lambert <email@hidden>
- Date: Mon, 19 Jan 2009 08:54:17 -0800
Warning: ERESTART is intended to be propagated up to the user/kernel
boundary to cause the system call to be redriven from user space buy
the system call stub.
We intentionally use this to unwind state that we can't otherwise
unwind. If you intercept this at the kernel level you will potentially
break things related to locking.
-- Terry
On Jan 19, 2009, at 2:17 AM, Quinn <email@hidden> wrote:
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
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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden