diff options
author | Rich Felker <dalias@aerifal.cx> | 2014-02-21 22:25:26 -0500 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2014-02-21 22:25:26 -0500 |
commit | dc01e2cbfb290198c03514fe51ed32c1098b774f (patch) | |
tree | 79357e35a582f1fea0012d1c9ff1faf4403c2c0e /src/internal | |
parent | fdb3efa5ddfa7120de98f8ae78b5f5dc9e8e2e71 (diff) | |
download | musl-dc01e2cbfb290198c03514fe51ed32c1098b774f.tar.gz musl-dc01e2cbfb290198c03514fe51ed32c1098b774f.tar.bz2 musl-dc01e2cbfb290198c03514fe51ed32c1098b774f.tar.xz musl-dc01e2cbfb290198c03514fe51ed32c1098b774f.zip |
add fallback emulation for accept4 on old kernels
the other atomic FD_CLOEXEC interfaces (dup3, pipe2, socket) already
had such emulation in place. the justification for doing the emulation
here is the same as for the other functions: it allows applications to
simply use accept4 rather than having to have their own fallback code
for ENOSYS/EINVAL (which one you get is arch-specific!) and there is
no reasonable way an application could benefit from knowing the
operation is emulated/non-atomic since there is no workaround at the
application level for non-atomicity (that is the whole reason these
interfaces were added).
Diffstat (limited to 'src/internal')
0 files changed, 0 insertions, 0 deletions