No cancel signal in unsafe places.
authorUlrich Drepper <drepper@redhat.com>
Fri, 15 May 2009 17:12:35 +0000 (10:12 -0700)
committerUlrich Drepper <drepper@redhat.com>
Fri, 15 May 2009 17:12:35 +0000 (10:12 -0700)
commitb1e74e1d80593ae1f2ed39f9d7eb37199205f774
treefb7ce319a3acac401040d173397132e8ea8ae765
parent2e180a26222caf478f29e272c9d1b5d9c6299752
No cancel signal in unsafe places.

When disabling async cancellation we cannot return from the function
call if the thread is canceled.  This happens when the cancel bits
have been set before async cancel is disabled but the signal hasn't
been sent/received yet.  Delay for as long as necessary since
otherwise the signal might be received in an unsafe context.
nptl/ChangeLog
nptl/cancellation.c
nptl/libc-cancellation.c