Do not attempt to reque a thread on a mutex queue. It may be that

a thread receives a spurious wakeup from sigtimedwait(), so make sure
that the call to the queueing code is called only once before entering
the loop (not in the loop). This should fix some fatal errors people
are seeing with messages stating the thread is already on the mutex queue.
These errors may still be triggered from signal handlers; however, since
that part of the code is not locked down yet.

1 files changed, 1 insertions, 1 deletions

diff --git a/lib/libthr/thread/thr_mutex.c b/lib/libthr/thread/thr_mutex.c
index 7d7c455..3244158 100644
--- a/lib/libthr/thread/thr_mutex.c
+++ b/lib/libthr/thread/thr_mutex.c
@@ -1406,8 +1406,8 @@ get_mcontested(pthread_mutex_t mutexp)
 	 * threads are concerned) setting of the thread state with
 	 * it's status on the mutex queue.
 	 */
+	mutex_queue_enq(mutexp, curthread);
 	do {
-		mutex_queue_enq(mutexp, curthread);
 		PTHREAD_SET_STATE(curthread, PS_MUTEX_WAIT);
 		curthread->data.mutex = mutexp;
 		_thread_critical_exit(curthread);