diff options
author | Rich Felker <dalias@aerifal.cx> | 2013-08-08 23:17:05 -0400 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2013-08-08 23:17:05 -0400 |
commit | d4d6d6f322cd13cfca2b179345cdcf67997c3529 (patch) | |
tree | 14f41853339c148be7315a2471d7123f3ae3239f /src/unistd/faccessat.c | |
parent | 72482f9020e4362b8d35849df6dca49f26d24c54 (diff) | |
download | musl-d4d6d6f322cd13cfca2b179345cdcf67997c3529.tar.gz musl-d4d6d6f322cd13cfca2b179345cdcf67997c3529.tar.bz2 musl-d4d6d6f322cd13cfca2b179345cdcf67997c3529.tar.xz musl-d4d6d6f322cd13cfca2b179345cdcf67997c3529.zip |
block signals during fork
there are several reasons for this. some of them are related to race
conditions that arise since fork is required to be async-signal-safe:
if fork or pthread_create is called from a signal handler after the
fork syscall has returned but before the subsequent userspace code has
finished, inconsistent state could result. also, there seem to be
kernel and/or strace bugs related to arrival of signals during fork,
at least on some versions, and simply blocking signals eliminates the
possibility of such bugs.
Diffstat (limited to 'src/unistd/faccessat.c')
0 files changed, 0 insertions, 0 deletions