[asterisk-dev] Re: deadlock in ast_custom_function_register?

[Tony Mountifield]

In article <8356131.1551161709440237.JavaMail.root at jupiler.digium.com>,
Russell Bryant <russell at digium.com> wrote:
> 
> ----- Tony Mountifield <tony at softins.clara.co.uk> wrote:
> > Asterisk relies on using recursive mutexes. If a process tries to
> > lock a mutex that it has already locked, it will succeed, and the "lock
> > count" of the mutex will be incremented. When it unlocks the mutex, the lock
> > count will be decremented. When this count reaches zero, the mutex
> > will really be unlocked and available for another process to lock.
> 
> Well, if you replace "process" with "thread" in what you have said,
> that is exactly correct.  :)

Yes, you're right; I was just using the term loosely. Poor show for
a programmer, I know! :-)

Cheers
Tony
-- 
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org