Losing features of JVM_Open, e.g. CLOEXEC

Christos Zoulas christos at zoulas.com
Thu Oct 30 18:35:36 UTC 2014

On Oct 30, 11:26am, martinrb at google.com (Martin Buchholz) wrote:
-- Subject: Re: Losing features of JVM_Open, e.g. CLOEXEC

| On Thu, Oct 30, 2014 at 10:52 AM, Mario Torre
| <neugens.limasoftware at gmail.com> wrote:
| > Indeed, but /proc/$PID/fd can perhaps be useful here? Not sure if this
| > can make a reasonable test though.
| Mario, I'm not sure what you mean.
| Even if we can find and inspect each fd, and even if we knew the
| stacktrace of where every fd was created, we still wouldn't know which
| close-on-exec flag should be cleared.

Let's not forget O_NOSIGPIPE, (and the equivalent SOCK_CLOEXEC and
SOCK_NOSIGPIPE, for socket(2)). Also all the dup*(), pipe*(),
kqueue*(), and fcntl() calls -- (in general all the system calls that
can create file descriptors).


More information about the core-libs-dev mailing list