diff options
author | Rich Felker <dalias@aerifal.cx> | 2014-03-24 16:57:11 -0400 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2014-03-24 16:57:11 -0400 |
commit | dab441aea240f3b7c18a26d2ef51979ea36c301c (patch) | |
tree | 9bb6c68bc3b025020a15d0d92b2b6aeff84a4d8c /src/process | |
parent | 98221c36119d2abfc55fe1d919705f625709fe3b (diff) | |
download | musl-dab441aea240f3b7c18a26d2ef51979ea36c301c.tar.gz musl-dab441aea240f3b7c18a26d2ef51979ea36c301c.tar.bz2 musl-dab441aea240f3b7c18a26d2ef51979ea36c301c.tar.xz musl-dab441aea240f3b7c18a26d2ef51979ea36c301c.zip |
always initialize thread pointer at program start
this is the first step in an overhaul aimed at greatly simplifying and
optimizing everything dealing with thread-local state.
previously, the thread pointer was initialized lazily on first access,
or at program startup if stack protector was in use, or at certain
random places where inconsistent state could be reached if it were not
initialized early. while believed to be fully correct, the logic was
fragile and non-obvious.
in the first phase of the thread pointer overhaul, support is retained
(and in some cases improved) for systems/situation where loading the
thread pointer fails, e.g. old kernels.
some notes on specific changes:
- the confusing use of libc.main_thread as an indicator that the
thread pointer is initialized is eliminated in favor of an explicit
has_thread_pointer predicate.
- sigaction no longer needs to ensure that the thread pointer is
initialized before installing a signal handler (this was needed to
prevent a situation where the signal handler caused the thread
pointer to be initialized and the subsequent sigreturn cleared it
again) but it still needs to ensure that implementation-internal
thread-related signals are not blocked.
- pthread tsd initialization for the main thread is deferred in a new
manner to minimize bloat in the static-linked __init_tp code.
- pthread_setcancelstate no longer needs special handling for the
situation before the thread pointer is initialized. it simply fails
on systems that cannot support a thread pointer, which are
non-conforming anyway.
- pthread_cleanup_push/pop now check for missing thread pointer and
nop themselves out in this case, so stdio no longer needs to avoid
the cancellable path when the thread pointer is not available.
a number of cases remain where certain interfaces may crash if the
system does not support a thread pointer. at this point, these should
be limited to pthread interfaces, and the number of such cases should
be fewer than before.
Diffstat (limited to 'src/process')
-rw-r--r-- | src/process/fork.c | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/src/process/fork.c b/src/process/fork.c index 1a82f428..864c7d7a 100644 --- a/src/process/fork.c +++ b/src/process/fork.c @@ -17,12 +17,11 @@ pid_t fork(void) __fork_handler(-1); __block_all_sigs(&set); ret = syscall(SYS_fork); - if (libc.main_thread && !ret) { + if (libc.has_thread_pointer && !ret) { pthread_t self = __pthread_self(); - self->tid = self->pid = syscall(SYS_getpid); + self->tid = self->pid = __syscall(SYS_getpid); memset(&self->robust_list, 0, sizeof self->robust_list); libc.threads_minus_1 = 0; - libc.main_thread = self; } __restore_sigs(&set); __fork_handler(!ret); |