diff options
author | Rich Felker <dalias@aerifal.cx> | 2019-02-17 21:46:14 -0500 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2019-02-17 21:46:14 -0500 |
commit | 805288929fdf511b4044cf07c59e02e2eaa9c546 (patch) | |
tree | fdd2cdfdea58d6b153923f2d7028e5e5e3ca8a5b /src/ldso/aarch64 | |
parent | 639bcf251e549f634da9a3e7ef8528eb2ec12505 (diff) | |
download | musl-805288929fdf511b4044cf07c59e02e2eaa9c546.tar.gz musl-805288929fdf511b4044cf07c59e02e2eaa9c546.tar.xz musl-805288929fdf511b4044cf07c59e02e2eaa9c546.zip |
fix data race between new pthread_key_delete and dtor execution
access to clear the entry in each thread's tsd array for the key being deleted was not synchronized with __pthread_tsd_run_dtors. I probably made this mistake from a mistaken belief that the thread list lock was held during the latter, which of course is not possible since it executes application code in a still-live-thread context. while we're at it, expand the interval during which signals are blocked to cover taking the write lock on key_lock, so that a signal at an inopportune time doesn't block forward progress of readers.
Diffstat (limited to 'src/ldso/aarch64')
0 files changed, 0 insertions, 0 deletions