Nick Mathewson 077b9f19a4 If SOCK_CLOEXEC and friends fail, fall back to regular socket() calls ... Since 0.2.3.1-alpha, we've supported the Linux extensions to socket(), open(), socketpair(), and accept() that enable us to create an fd and make it close-on-exec with a single syscall. This not only saves us a syscall (big deal), but makes us less vulnerable to race conditions where we open a socket and then exec before we can make it close-on-exec. But these extensions are not supported on all Linuxes: They were added between 2.6.23 or so and 2.6.28 or so. If you were to build your Tor against a recent Linux's kernel headers, and then run it with a older kernel, you would find yourselve unable to open sockets. Ouch! The solution here is that, when one of these syscalls fails with EINVAL, we should try again in the portable way. This adds an extra syscall in the case where we built with new headers and are running with old ones, but it will at least allow Tor to work. Fixes bug 5112; bugfix on 0.2.3.1-alpha.		2012-02-14 10:34:06 -05:00
..
bug5112	If SOCK_CLOEXEC and friends fail, fall back to regular socket() calls	2012-02-14 10:34:06 -05:00
tinytest_update	Synchronize with upstream tinytest again: remove _identifiers	2012-02-13 17:45:15 -05:00