From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Difficulty emulating F_DUPFD_CLOEXEC
Date: Sat, 23 Mar 2013 22:09:10 -0400 [thread overview]
Message-ID: <20130324020910.GZ20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130324015923.GA5905@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 217 bytes --]
On Sat, Mar 23, 2013 at 09:59:23PM -0400, Rich Felker wrote:
> This uglifies fcntl.c a bit more, but I think it works. Does the above
> reasoning make sense? Any other ideas?
Proposed patch attached. Untested.
Rich
[-- Attachment #2: fcntl.diff --]
[-- Type: text/plain, Size: 779 bytes --]
diff --git a/src/fcntl/fcntl.c b/src/fcntl/fcntl.c
index fb7806a..3e7da2a 100644
--- a/src/fcntl/fcntl.c
+++ b/src/fcntl/fcntl.c
@@ -22,5 +22,17 @@ int fcntl(int fd, int cmd, ...)
if (ret) return __syscall_ret(ret);
return ex.type == F_OWNER_PGRP ? -ex.pid : ex.pid;
}
+ if (cmd == F_DUPFD_CLOEXEC) {
+ int ret = __syscall(SYS_fcntl, fd, F_DUPFD_CLOEXEC, arg);
+ if (ret != -EINVAL) return __syscall_ret(ret);
+ ret = __syscall(SYS_fcntl, fd, F_DUPFD_CLOEXEC, 0);
+ if (ret != -EINVAL) {
+ if (ret >= 0) __syscall(SYS_close, ret);
+ return __syscall_ret(-EINVAL);
+ }
+ ret = __syscall(SYS_fcntl, fd, F_DUPFD, arg);
+ if (ret >= 0) __syscall(SYS_fcntl, ret, F_SETFD, FD_CLOEXEC);
+ return __syscall_ret(ret);
+ }
return syscall(SYS_fcntl, fd, cmd, arg);
}
next prev parent reply other threads:[~2013-03-24 2:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 1:59 Rich Felker
2013-03-24 2:09 ` Rich Felker [this message]
2013-03-24 2:12 ` Rich Felker
2013-03-24 2:10 ` Zvi Gilboa
2013-03-24 2:14 ` Szabolcs Nagy
2013-03-24 2:17 ` Rich Felker
2013-03-24 2:27 ` Zvi Gilboa
2013-03-24 2:33 ` Rich Felker
2013-03-24 2:57 ` Zvi Gilboa
2013-03-24 3:08 ` Rich Felker
2013-03-24 23:51 ` Rob Landley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130324020910.GZ20323@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).