mirror of
git://git.musl-libc.org/musl
synced 2025-02-01 03:21:33 +00:00
484194dbf4
i386, x86_64, x32, and powerpc all use TLS for stack protector canary values in the default stack protector ABI, but the location only matched the ABI on i386 and x86_64. on x32, the expected location for the canary contained the tid, thus producing spurious mismatches (resulting in process termination) upon fork. on powerpc, the expected location contained the stdio_locks list head, so returning from a function after calling flockfile produced spurious mismatches. in both cases, the random canary was not present, and a predictable value was used instead, making the stack protector hardening much less effective than it should be. in the current fix, the thread structure has been expanded to have canary fields at all three possible locations, and archs that use a non-default location must define a macro in pthread_arch.h to choose which location is used. for most archs (which lack TLS canary ABI) the choice does not matter. |
||
|---|---|---|
| .. | ||
| bits | ||
| src | ||
| atomic.h | ||
| crt_arch.h | ||
| pthread_arch.h | ||
| reloc.h | ||
| syscall_arch.h | ||