mit krb5 and threads - api

[Jeffrey Altman]

Ken Raeburn wrote:

>
>> OpenAFS has run into some problems because developers
>> make the assumption that mutexes can be safe locked
>> twice within the same thread.  This has lead to some
>> interesting deadlock situations which are difficult
>> to debug.
>
>
> Sounds like another good reason to require simple locks.
>
> Ken

It is because the locks are simple that the problems
have occurred.  A thread locks something and calls into
a function which then attempts to lock the same thing
and deadlocks.