xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: wei.liu2@citrix.com, andrew.cooper3@citrix.com,
	ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v2] xl: close nullfd after dup2'ing it to stdin
Date: Mon, 29 Feb 2016 10:45:51 -0500	[thread overview]
Message-ID: <20160229154551.GA28725@char.us.oracle.com> (raw)
In-Reply-To: <1456223431.6225.124.camel@citrix.com>

On Tue, Feb 23, 2016 at 10:30:31AM +0000, Ian Campbell wrote:
> On Wed, 2016-02-17 at 10:39 +0000, Ian Campbell wrote:
> > We assert that nullfd if not std{in,out,err} since that would result
> > in closing one of the just dup2'd fds. For this to happen
> > std{in,out,err} would have needed to be closed, at which point all
> > sorts of other things could go wrong.
> > 
> > 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
> 
> ping?

Ian, you wouldn't have a git branch with all your outstanding
patches you had posted somewhere?

Just in case we don't get to them done by feature freeze window and
somebody starts replaying these patches..

> 
> > ---
> > v2: Assert logfile and nullfd are not stdio fds
> > ---
> >  tools/libxl/xl_cmdimpl.c | 5 +++++
> >  1 file changed, 5 insertions(+)
> > 
> > diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
> > index 9958d8a..a377de1 100644
> > --- a/tools/libxl/xl_cmdimpl.c
> > +++ b/tools/libxl/xl_cmdimpl.c
> > @@ -499,12 +499,17 @@ static int do_daemonize(char *name, const char
> > *pidfile)
> >  
> >      CHK_SYSCALL(logfile = open(fullname, O_WRONLY|O_CREAT|O_APPEND,
> > 0644));
> >      free(fullname);
> > +    assert(logfile >= 3);
> >  
> >      CHK_SYSCALL(nullfd = open("/dev/null", O_RDONLY));
> > +    assert(nullfd >= 3);
> > +
> >      dup2(nullfd, 0);
> >      dup2(logfile, 1);
> >      dup2(logfile, 2);
> >  
> > +    close(nullfd);
> > +
> >      CHK_SYSCALL(daemon(0, 1));
> >  
> >      if (pidfile) {
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-02-29 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 11:35 [PATCH] xl: close nullfd after dup2'ing it to stdin Ian Campbell
2016-02-16 13:06 ` 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 [this message]
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=20160229154551.GA28725@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@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).