diff options
| author | Rich Felker <dalias@aerifal.cx> | 2013-08-31 01:12:00 -0400 |
|---|---|---|
| committer | Rich Felker <dalias@aerifal.cx> | 2013-08-31 01:12:00 -0400 |
| commit | 7cc49f98a2b5346259d2209ba14d7c18959f9369 (patch) | |
| tree | b51534ed3320b2621a59d4bd9d70b8a83ed8409f /src/signal/getitimer.c | |
| parent | d0f0fa484c5216710936715c176f67b3781e4b71 (diff) | |
| download | musl-7cc49f98a2b5346259d2209ba14d7c18959f9369.tar.gz musl-7cc49f98a2b5346259d2209ba14d7c18959f9369.tar.xz musl-7cc49f98a2b5346259d2209ba14d7c18959f9369.zip | |
fix breakage in synccall due to incorrect signal restoration in sigqueue
commit 07827d1a82fb33262f686eda959857f0d28cd8fa seems to have introduced this issue. sigqueue is called from the synccall core, at which time, even implementation-internal signals are blocked. however, pthread_sigmask removes the implementation-internal signals from the old mask before returning, so that a process which began life with them blocked will not be able to save a signal mask that has them blocked, possibly causing them to become re-blocked later. however, this was causing sigqueue to unblock the implementation-internal signals during synccall, leading to deadlock.
Diffstat (limited to 'src/signal/getitimer.c')
0 files changed, 0 insertions, 0 deletions