Hi Robert, Robert Millan wrote: > This isn't a kernel bug. The kernel recognizes O_CLOEXEC properly > when userland uses it. > > The problem is that userland isn't actually using O_CLOEXEC, because > its declaration is missing in glibc headers. Actually it's already > been reported: see #679198. When did O_CLOEXEC get involved? This report was about a use of FD_CLOEXEC. Thanks, Jonathan