site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pcpitstop.com; s=google; h=from:to:subject:thread-topic:thread-index:date:message-id :accept-language:content-language:mime-version; bh=kenwLzUZHQ3lObASi9AvXWSccmfs46xtTzE6tVxR51k=; b=lBJ5sXkQ8EgM2GX4ycHg1WGIpBV9SEjAodq+adbHuwzrnysJo69jzxPxWzIHPejUYw ZABxpVclNfmsCtr4iGAznfjjyBlTFXG+4WTxR6v+I1B3bE9wYUIQ0DaJc9ZRKeYnO3x3 jFGdjjmB7rbcGDaqdve71BOvQS/oHQ7J2/N1Y= Thread-index: AQHUvw9rl8vv0pdDSEOWrbDB0st79g== 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 (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com