Unexpected behavior using msleep in a KAUTH_SCOPE_VNODE handler
Unexpected behavior using msleep in a KAUTH_SCOPE_VNODE handler
- Subject: Unexpected behavior using msleep in a KAUTH_SCOPE_VNODE handler
- From: Matt Riley <email@hidden>
- Date: Thu, 07 Feb 2019 18:03:24 +0000
- Thread-topic: Unexpected behavior using msleep in a KAUTH_SCOPE_VNODE handler
Currently, we are using a KAUTH_SCOPE_VNODE listener and are waiting for
results from a user level process with an msleep call.
When sleeping in this context we see that when executing some applications we
do not see any activity in the listener until the msleep finishes while other
applications seem to correctly flow to the handler.
We also see some applications become non-responsive even though they are not
trying to execute anything at the time, specifically Terminal output appears
frozen, while other applications appear to continue running correctly.
I guess my question is – what is the proper way to wait in the kernel extension
if not msleep/wakeup? Or is it simply not possible to wait in the listener and
expect other applications to continue correctly?
_______________________________________________
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