Open Radar

 
Area:
Performance (slow, hung)

Summary:
Executing pthread_cancel shortly after pthread_create might lead to the cancel request being lost. This is in violation of POSIX, as by the time pthread_create returns, use of the pthread_t in pthread_cancel should be valid.

Steps to Reproduce:
1. Compile the attached cancel.c file
2. Run following shell command 
for i in `seq 100000`; do ./a.out $i ; done && echo ' All is well!'


Expected Results:
Shell command will count to 100000 and finish with a "100000 All is well!"

Actual Results:
The command will hang, usually before $i reached 1000, because the cancellation request was lost.

LLDB inspection shows that the thread is blocking on read as expected. If the user call pthread_cancel(pthread) manually on main's frame, the thread is cancelled. So it seems, there's a race between pthread_create and pthread_cancel.

Version:
macOS Sierrra v10.12.3
/usr/lib/system/libsystem_pthread.dylib (compatibility version 1.0.0, current version 218.30.1)

Notes:


Configuration:
macOS Sierrra v10.12.3
/usr/lib/system/libsystem_pthread.dylib (compatibility version 1.0.0, current version 218.30.1)

Attachments:
'cancel.c' was successfully uploaded.

See https://gist.github.com/a3f/0fe444521feca3096fc91e0bfddc1a2c