From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com, wei.liu2@citrix.com, xen-devel@lists.xen.org
Cc: andrew.cooper3@citrix.com, Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH] xl: close nullfd after dup2'ing it to stdin
Date: Tue, 16 Feb 2016 11:35:45 +0000 [thread overview]
Message-ID: <1455622545-22269-1-git-send-email-ian.campbell@citrix.com> (raw)
Taking care not to do so if nullfd happens (somehow) to have the same
fd number as stdin/out/err.
CID: 1130519
It was previously hypothesised[0] that fixing 1130516 would solve this
too, but that appears to not have been the case.
Compile tested only.
[0] http://lists.xenproject.org/archives/html/xen-devel/2013-11/msg02931.html
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Cc: andrew.cooper3@citrix.com
---
tools/libxl/xl_cmdimpl.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
index d07ccb2..f38e3dd 100644
--- a/tools/libxl/xl_cmdimpl.c
+++ b/tools/libxl/xl_cmdimpl.c
@@ -505,6 +505,16 @@ static int do_daemonize(char *name, const char *pidfile)
dup2(logfile, 1);
dup2(logfile, 2);
+ /* Close nullfd unless it happens to == std{in,out,err} */
+ switch (nullfd) {
+ case 0:
+ case 1:
+ case 2:
+ break;
+ default:
+ close(nullfd);
+ }
+
CHK_SYSCALL(daemon(0, 1));
if (pidfile) {
--
2.1.4
next reply other threads:[~2016-02-16 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 11:35 Ian Campbell [this message]
2016-02-16 13:06 ` [PATCH] xl: close nullfd after dup2'ing it to stdin Wei Liu
2016-02-16 17:45 ` Ian Jackson
2016-02-16 21:54 ` Ian Campbell
2016-02-17 10:39 ` [PATCH v2] " Ian Campbell
2016-02-23 10:30 ` Ian Campbell
2016-02-29 15:45 ` Konrad Rzeszutek Wilk
2016-03-01 12:54 ` Wei Liu
2016-03-01 13:40 ` Ian Jackson
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=1455622545-22269-1-git-send-email-ian.campbell@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.
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).