summaryrefslogtreecommitdiff
path: root/crypt
diff options
context:
space:
mode:
authorSiddhesh Poyarekar <siddhesh@redhat.com>2012-10-10 12:17:27 +0530
committerSiddhesh Poyarekar <siddhesh@redhat.com>2012-10-10 12:52:56 +0530
commit0e3b5d6a6859d74a18033d3a55e0ee92340437b3 (patch)
treeb4f8c7fe139fb80e4fba77409942b68942a5df48 /crypt
parentf96f12423a1b801f4a198f2568e29e85bd9cc473 (diff)
downloadglibc-0e3b5d6a6859d74a18033d3a55e0ee92340437b3.tar.gz
Take lock in pthread_cond_wait cleanup handler only when needed
[BZ #14652] When a thread waiting in pthread_cond_wait with a PI mutex is cancelled after it has returned successfully from the futex syscall but just before async cancellation is disabled, it enters its cancellation handler with the mutex held and simply calling a mutex_lock again will result in a deadlock. Hence, it is necessary to see if the thread owns the lock and try to lock it only if it doesn't.
Diffstat (limited to 'crypt')
0 files changed, 0 insertions, 0 deletions