Ben Noordhuis 27cd5f03ef linux: fix accept4() ENOSYS detection on i386 ... accept4() piggybacks on the socketcall() on i386. socketcall() has the flaw that it returns EINVAL instead of ENOSYS when the operation is not supported. The problem is that accept4() also returns EINVAL when its flag argument is invalid. Try to discern between the two failure cases to the best of our abilities.		2012-06-29 02:11:45 +02:00
..
eio	eio: don't use futimes() on linux	2012-02-06 20:35:56 +01:00
ev
linux	linux: fix accept4() ENOSYS detection on i386	2012-06-29 02:11:45 +02:00
async.c
core.c
cygwin.c
darwin.c
dl.c
error.c
freebsd.c	unix, test: make NANOSEC a 64 bits unsigned int	2012-06-07 17:00:01 +02:00
fs.c
internal.h	unix: simplify uv__make_pipe() and uv__make_socketpair()	2012-06-11 02:47:39 +02:00
kqueue.c
loop-watcher.c
loop.c
netbsd.c
openbsd.c	unix, test: make NANOSEC a 64 bits unsigned int	2012-06-07 17:00:01 +02:00
pipe.c
poll.c
process.c	unix: always set CLOEXEC flag for child process stdio FDs	2012-06-14 18:29:47 +02:00
stream.c
sunos.c
tcp.c
thread.c
timer.c
tty.c
udp.c
uv-eio.c
uv-eio.h