[Bug 329] linuxthreads.old: Issues with pthread_mutex_lock()

bugzilla at busybox.net bugzilla at busybox.net
Tue May 12 14:55:04 UTC 2009


https://bugs.busybox.net/show_bug.cgi?id=329


Timo Teräs <timo.teras at iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |timo.teras at iki.fi




--- Comment #5 from Timo Teräs <timo.teras at iki.fi>  2009-05-12 14:55:03 UTC ---
One problem is (for PTHREAD_MUTEX_ERRORCHECK_NP and PTHREAD_MUTEX_TIMED_NP)
types that __pthread_alt_lock() uses wait_node on stack, but does not protect
against signals. It is possible for the wait_node on stack to be left on the
wake up queue, but the pthread_alt_lock to be unwinded from stack causing bad
things.

I suspect same can happen with __pthread_lock(). However, __pthread_lock() does
not link stack allocated items on the wait list, so it's harder to debug. But I
suspect similar race condition exists there.

manpage says pthread_mutex_lock is not a cancellation point. Shouldn't we just
block signals there?


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the uClibc-cvs mailing list