|author||Rich Felker <email@example.com>||2013-08-03 13:20:42 -0400|
|committer||Rich Felker <firstname.lastname@example.org>||2013-08-03 13:20:42 -0400|
fix multiple bugs in SIGEV_THREAD timers
1. the thread result field was reused for storing a kernel timer id, but would be overwritten if the application code exited or cancelled the thread. 2. low pointer values were used as the indicator that the timer id is a kernel timer id rather than a thread id. this is not portable, as mmap may return low pointers on some conditions. instead, use the fact that pointers must be aligned and kernel timer ids must be non-negative to map pointers into the negative integer space. 3. signals were not blocked until after the timer thread started, so a race condition could allow a signal handler to run in the timer thread when it's not supposed to exist. this is mainly problematic if the calling thread was the only thread where the signal was unblocked and the signal handler assumes it runs in that thread.
Diffstat (limited to 'src/env')
0 files changed, 0 insertions, 0 deletions