All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] io: some fixes to handling of /dev/null when running commands
Date: Mon, 11 Jan 2016 22:02:02 +0100	[thread overview]
Message-ID: <5694184A.8000501@redhat.com> (raw)
In-Reply-To: <1452517549-8515-1-git-send-email-berrange@redhat.com>



On 11/01/2016 14:05, Daniel P. Berrange wrote:
> The /dev/null file handle was leaked in a couple of places.
> There is also the possibility that both readfd and writefd
> point to the same /dev/null file handle, so care must be
> taken not to close the same file handle twice.
> 
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
>  io/channel-command.c | 22 ++++++++++++++++------
>  1 file changed, 16 insertions(+), 6 deletions(-)
> 
> diff --git a/io/channel-command.c b/io/channel-command.c
> index a220fe8..a9c67aa 100644
> --- a/io/channel-command.c
> +++ b/io/channel-command.c
> @@ -66,7 +66,7 @@ qio_channel_command_new_spawn(const char *const argv[],
>  
>      if (stdinnull || stdoutnull) {
>          devnull = open("/dev/null", O_RDWR);
> -        if (!devnull) {
> +        if (devnull < 0) {
>              error_setg_errno(errp, errno,
>                               "Unable to open /dev/null");
>              goto error;
> @@ -98,6 +98,9 @@ qio_channel_command_new_spawn(const char *const argv[],
>              close(stdoutfd[0]);
>              close(stdoutfd[1]);
>          }
> +        if (devnull != -1) {
> +            close(devnull);
> +        }
>  
>          execv(argv[0], (char * const *)argv);
>          _exit(1);
> @@ -117,6 +120,9 @@ qio_channel_command_new_spawn(const char *const argv[],
>      return ioc;
>  
>   error:
> +    if (devnull != -1) {
> +        close(devnull);
> +    }
>      if (stdinfd[0] != -1) {
>          close(stdinfd[0]);
>      }
> @@ -202,12 +208,12 @@ static void qio_channel_command_finalize(Object *obj)
>      QIOChannelCommand *ioc = QIO_CHANNEL_COMMAND(obj);
>      if (ioc->readfd != -1) {
>          close(ioc->readfd);
> -        ioc->readfd = -1;
>      }
> -    if (ioc->writefd != -1) {
> +    if (ioc->writefd != -1 &&
> +        ioc->writefd != ioc->readfd) {
>          close(ioc->writefd);
> -        ioc->writefd = -1;
>      }
> +    ioc->writefd = ioc->readfd = -1;
>      if (ioc->pid > 0) {
>  #ifndef WIN32
>          qio_channel_command_abort(ioc, NULL);
> @@ -299,12 +305,16 @@ static int qio_channel_command_close(QIOChannel *ioc,
>      /* We close FDs before killing, because that
>       * gives a better chance of clean shutdown
>       */
> -    if (close(cioc->writefd) < 0) {
> +    if (cioc->readfd != -1 &&
> +        close(cioc->readfd) < 0) {
>          rv = -1;
>      }
> -    if (close(cioc->readfd) < 0) {
> +    if (cioc->writefd != -1 &&
> +        cioc->writefd != cioc->readfd &&
> +        close(cioc->writefd) < 0) {
>          rv = -1;
>      }
> +    cioc->writefd = cioc->readfd = -1;
>  #ifndef WIN32
>      if (qio_channel_command_abort(cioc, errp) < 0) {
>          return -1;
> 

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

      reply	other threads:[~2016-01-11 21:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 13:05 [Qemu-devel] [PATCH] io: some fixes to handling of /dev/null when running commands Daniel P. Berrange
2016-01-11 21:02 ` Paolo Bonzini [this message]

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=5694184A.8000501@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.