Re: KEXT/KAUTH, malloc-related crash, login only?!?
Re: KEXT/KAUTH, malloc-related crash, login only?!?
- Subject: Re: KEXT/KAUTH, malloc-related crash, login only?!?
- From: Ondra Cada <email@hidden>
- Date: Wed, 7 Mar 2007 14:46:43 +0100
Terry,
On 7.3.2007, at 13:40, Terry Lambert wrote:
It might be important that, like Kauthorama does, when the limit
is reached I don't cease malloc'ing; instead, for each malloc I
release the oldest queued item. Essentially, the algorithm is
alloc_item
if (OK) {
alloc_and_fill_names
if (OK) {
if (limit_reached) dequeue_last
enqueue_item
}
}
How do you protect your queue against reentrancy by multiple
threads of control, resulting in corruption of the queue?
Using locks (lck_mtx_lock/unlock). That's irrelevant to the problem
though: the KEXT crashes even if the queue access is completely
commented out.
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
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