diff options
| author |   Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2019-12-09 14:33:33 -0300 |
|---|---|---|
| committer | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2020-02-19 13:46:31 -0300 |
| commit | 27d83441a2f900059d0421339d0e8c27220ffa36 (patch) | |
| tree | 22b8a2d04bfc965462d96a99b32da18fc17eb2b5 /support/tst-test_compare_blob.c | |
| parent | Fix tst-pkey expectations on pkey_get [BZ #23202] (diff) | |
| download | glibc-27d83441a2f900059d0421339d0e8c27220ffa36.tar.gz glibc-27d83441a2f900059d0421339d0e8c27220ffa36.tar.bz2 glibc-27d83441a2f900059d0421339d0e8c27220ffa36.zip | |
Block all signals on timer_create thread (BZ#10815)
The behavior of the signal mask on threads created by timer_create
for SIGEV_THREAD timers are implementation-defined and glibc explicit
unblocks all signals before calling the user-defined function.
This behavior, although not incorrect standard-wise, opens a race if a
program using a blocked rt-signal plus sigwaitinfo (and without an
installed signal handler for the rt-signal) receives a signal while
executing the used-defined function for SIGEV_THREAD.
A better alternative discussed in bug report is to rather block all
signals (besides the internal ones not available to application
usage).
This patch fixes this issue by only unblocking SIGSETXID (used on
set*uid function) and SIGCANCEL (used for thread cancellation).
Checked on x86_64-linux-gnu and i686-linux-gnu.
Diffstat (limited to 'support/tst-test_compare_blob.c')
0 files changed, 0 insertions, 0 deletions