|author||Rich Felker <email@example.com>||2015-03-16 20:12:49 -0400|
|committer||Rich Felker <firstname.lastname@example.org>||2015-03-16 20:12:49 -0400|
block all signals (even internal ones) in cancellation signal handler
previously the implementation-internal signal used for multithreaded set*id operations was left unblocked during handling of the cancellation signal. however, on some archs, signal contexts are huge (up to 5k) and the possibility of nested signal handlers drastically increases the minimum stack requirement. since the cancellation signal handler will do its job and return in bounded time before possibly passing execution to application code, there is no need to allow other signals to interrupt it.
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions