|author||Rich Felker <email@example.com>||2019-09-13 14:17:36 -0400|
|committer||Rich Felker <firstname.lastname@example.org>||2019-09-13 14:17:36 -0400|
harden thread start with failed scheduling against broken __clone
commit 8a544ee3a2a75af278145b09531177cab4939b41 introduced a dependency of the failure path for explicit scheduling at thread creation on __clone's handling of the start function returning, which should result in SYS_exit. as noted in commit 05870abeaac0588fb9115cfd11f96880a0af2108, the arm version of __clone was broken in this case. in the past, the mips version was also broken; it was fixed in commit 8b2b61e0001281be0dcd3dedc899bf187172fecb. since this code path is pretty much entirely untested (previously only reachable in applications that call the public clone() and return from the start function) and consists of fragile per-arch asm, don't assume it works, at least not until it's been thoroughly tested. instead make the SYS_exit syscall from the start function's failure path.
Diffstat (limited to 'src/thread/pthread_rwlock_tryrdlock.c')
0 files changed, 0 insertions, 0 deletions