Re: initialized state of capability objects should be locked

[Neal H. Walfield]

> I don't think so.  Taking a mutex is, maybe not in our current
> implementations, but certainly at the abstract level, something that
> is inherently tied to the thread performing the operation.  A locked
> mutex would have to be unlocked by the thread taking the lock.  This
> disallows sharing a locked mutex object via a pool common to all
> threads.
> 
> Now, you may be able to argue that our current pthread implementations
> don't actually make any distinction (for example, we may not implement
> checked mutex's etc).  But even if this is true (I haven't checked), I
> don't think this is a sane optimization to make (and for what I think
> are pretty obvious reasons).

You are right.

Our libpthread doesn't require that the same thread which locks a
mutex unlock it but using this knowledge will only get us into trouble
later for a trivial micro-optimization.

Thanks,
Neal