Re: __synclock_lock(), pthread_cond_wait(...) and spurious wake-ups

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



never mind this, people
this was in haste



On Thu, Jun 15, 2017 at 9:49 AM, Milind Changire <mchangir@xxxxxxxxxx> 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

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux