use direct syscall rather than write function in posix_spawn child
authorRich Felker <dalias@aerifal.cx>
Sat, 6 Dec 2014 02:19:39 +0000 (21:19 -0500)
committerRich Felker <dalias@aerifal.cx>
Sat, 6 Dec 2014 02:19:39 +0000 (21:19 -0500)
commit8f7bc690f07e90177b176b6e19736ad7c1d49840
tree06f4886843fe4f623a6d5ca7dec851434d7d7170
parent1c12c24364d1058ffdbb28fca72a51de85082778
use direct syscall rather than write function in posix_spawn child

the write function is a cancellation point and accesses thread-local
state belonging to the calling thread in the parent process. since
cancellation is blocked for the duration of posix_spawn, this is
probably safe, but it's fragile and unnecessary. making the syscall
directly is just as easy and clearly safe.
src/process/posix_spawn.c