Bug#261237: NPTL: pthread_cond_timedwait with timespec in the past destroys cond variable

[GOTO Masanori <gotom@debian.or.jp>]

tags 261237 confirmed fixed-upstream
thanks

At Sat, 24 Jul 2004 13:59:32 +0200,
Hubert Schmid wrote:
> pthread_cond_timedwait with a timespec in the past sometimes destroys
> the pthread_cond_t variable. The following pthread_cond_(timed)wait
> calls ignore all signals on the condition variable and block.
> 
> There is no Workaround, because I cannot guarantee that the timespec is
> really in the future (because the thread may be interrupted between
> gettimeofday and pthread_cond_timedwait).
> 
> The problem only occurs with NPTL (i.e. I can't reproduce the problem
> with LD_ASSUME_KERNEL=2.4.19).
> 
> The following program deadlocks after some iterations (10-1000).

I tested and I confirmed your test code goes sometimes deadlock.  But
the latest nptl are not blocked.  I tagged it as fixed-upstream.

Regards,
-- gotom