Say you have this code
pthread_mutex_lock(&cam->video_lock);
while(cam->status == WAIT_DISPLAY) // <-- Why is this a \'while\' and not an \'if\'
It is recommended that all threads check the condition after returning from pthread_cond_wait because there are several reasons the condition might not be true. One of these reasons is a spurious wakeup; that is, a thread might get woken up even though no thread signalled the condition.
Source : Spurious wakeup
Spurious wakeups are one reason, but legitimate but extraneous wakeups are another.
Consider:
You put a job on a queue.
You signal the condition variable, waking thread A.
You put a job on a queue.
You signal the condition variable, waking thread B.
Thread A gets scheduled, does the first job.
Thread A finds the queue non-empty and does the second job.
Thread B gets scheduled, having been woken, but finds the queue still empty.
For performance reasons, the POSIX API allows the OS to wake up your thread even if the condition has not been fulfilled (that's called a spurious wakeup).