[Gluster-devel] __synclock_lock(), pthread_cond_wait(...) and spurious wake-ups

Milind Changire mchangir at redhat.com
Thu Jun 15 04:26:01 UTC 2017


never mind this, people
this was in haste



On Thu, Jun 15, 2017 at 9:49 AM, Milind Changire <mchangir at redhat.com>
wrote:

> in __synclock_lock ( ) there's a pthread_cond_wait (&lock->cond,
> &lock->guard); near the end of the function ...
>
> shouldn't the return value of pthread_cond_wait (...) be checked in a
> while loop to test for spurious wake-ups and also test the logical state
> that the lock variable to be in to hold ?
>
> --
> Milind
>
>


-- 
Milind
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170615/62d5de37/attachment.html>


More information about the Gluster-devel mailing list