4cd18a22d5
followed are: Only 3 functions (pthread_cancel, pthread_setcancelstate, pthread_setcanceltype) are required to be async-signal-safe by POSIX. None of the rest of the pthread api is required to be async-signal-safe. This means that only the three mentioned functions are safe to use from inside signal handlers. However, there are certain system/libc calls that are cancellation points that a caller may call from within a signal handler, and since they are cancellation points calls have to be made into libthr to test for cancellation and exit the thread if necessary. So, the cancellation test and thread exit code paths must be async-signal-safe as well. A summary of the changes follows: o Almost all of the code paths that masked signals, as well as locking the pthread structure now lock only the pthread structure. o Signals are masked (and left that way) as soon as a thread enters pthread_exit(). o The active and dead threads locks now explicitly require that signals are masked. o Access to the isdead field of the pthread structure is protected by both the active and dead list locks for writing. Either one is sufficient for reading. o The thread state and type fields have been combined into one three-state switch to make it easier to read without requiring a lock. It doesn't need a lock for writing (and therefore for reading either) because only the current thread can write to it and it is an integer value. o The thread state field of the pthread structure has been eliminated. It was an unnecessary field that mostly duplicated the flags field, but required additional locking that would make a lot more code paths require signal masking. Any truly unique values (such as PS_DEAD) have been reborn as separate members of the pthread structure. o Since the mutex and condvar pthread functions are not async-signal-safe there is no need to muck about with the wait queues when handling a signal ... o ... which also removes the need for wrapping signal handlers and sigaction(2). o The condvar and mutex async-cancellation code had to be revised as a result of some of these changes, which resulted in semi-unrelated changes which would have been difficult to work on as a separate commit, so they are included as well. The only part of the changes I am worried about is related to locking for the pthread joining fields. But, I will take a closer look at them once this mega-patch is committed.
52 lines
854 B
Makefile
52 lines
854 B
Makefile
# $FreeBSD$
|
|
|
|
# thr sources
|
|
.PATH: ${.CURDIR}/thread
|
|
|
|
SRCS+= \
|
|
thr_attr.c \
|
|
thr_autoinit.c \
|
|
thr_barrier.c \
|
|
thr_barrierattr.c \
|
|
thr_cancel.c \
|
|
thr_clean.c \
|
|
thr_concurrency.c \
|
|
thr_cond.c \
|
|
thr_condattr_destroy.c \
|
|
thr_condattr_init.c \
|
|
thr_create.c \
|
|
thr_detach.c \
|
|
thr_equal.c \
|
|
thr_exit.c \
|
|
thr_find_thread.c \
|
|
thr_getprio.c \
|
|
thr_init.c \
|
|
thr_join.c \
|
|
thr_kern.c \
|
|
thr_main_np.c \
|
|
thr_mattr_init.c \
|
|
thr_mattr_kind_np.c \
|
|
thr_multi_np.c \
|
|
thr_mutex.c \
|
|
thr_mutex_prioceiling.c \
|
|
thr_mutex_protocol.c \
|
|
thr_mutexattr_destroy.c \
|
|
thr_once.c \
|
|
thr_printf.c \
|
|
thr_resume_np.c \
|
|
thr_rwlock.c \
|
|
thr_rwlockattr.c \
|
|
thr_self.c \
|
|
thr_sem.c \
|
|
thr_seterrno.c \
|
|
thr_setprio.c \
|
|
thr_setschedparam.c \
|
|
thr_sig.c \
|
|
thr_spec.c \
|
|
thr_spinlock.c \
|
|
thr_stack.c \
|
|
thr_subr.c \
|
|
thr_suspend_np.c \
|
|
thr_syscalls.c \
|
|
thr_yield.c
|