All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Lei Li <lilei@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-char: inherit ptys and imporve output from -serial pty
Date: Thu, 20 Dec 2012 16:19:39 +0100	[thread overview]
Message-ID: <87bodohhtg.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <1356014948-13450-1-git-send-email-lilei@linux.vnet.ibm.com> (Lei Li's message of "Thu, 20 Dec 2012 22:49:08 +0800")

Lei Li <lilei@linux.vnet.ibm.com> writes:

> When controlling a qemu instance from another program, it's
> hard to know which serial port or monitor device is redirected
> to which pty. With more than one device using "pty" a lot of
> guesswork is involved.
>
> $ ./x86_64-softmmu/qemu-system-x86_64 -serial pty -serial pty -monitor pty
> char device redirected to /dev/pts/5
> char device redirected to /dev/pts/6
> char device redirected to /dev/pts/7
>
> Although we can find out what everything else is connected to
> by the "info chardev" with "-monitor stdio" in the command line,
> It'd be very useful to be able to have qemu inherit pseudo-tty
> file descriptors so they could just be specified on the command
> line like:
>
> $ ./x86_64-softmmu/qemu-system-x86_64 -serial pty -serial pty -monitor pty
> char device compat_monitor0 redirected to /dev/pts/5
> char device serial0 redirected to /dev/pts/6
> char device serial1 redirected to /dev/pts/7
>
> Referred link: https://bugs.launchpad.net/qemu/+bug/938552
>
> Reported-by: Craig Ringer <ringerc@gmail.com>
> Signed-off-by: Lei Li <lilei@linux.vnet.ibm.com>
> ---
>  qemu-char.c |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/qemu-char.c b/qemu-char.c
> index 242b799..2b0f5f4 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -981,6 +981,7 @@ static CharDriverState *qemu_chr_open_pty(QemuOpts *opts)
>      CharDriverState *chr;
>      PtyCharDriver *s;
>      struct termios tty;
> +    char *label;
>      int master_fd, slave_fd, len;
>  #if defined(__OpenBSD__) || defined(__DragonFly__)
>      char pty_name[PATH_MAX];
> @@ -1006,7 +1007,8 @@ static CharDriverState *qemu_chr_open_pty(QemuOpts *opts)
>      chr->filename = g_malloc(len);
>      snprintf(chr->filename, len, "pty:%s", q_ptsname(master_fd));
>      qemu_opt_set(opts, "path", q_ptsname(master_fd));
> -    fprintf(stderr, "char device redirected to %s\n", q_ptsname(master_fd));
> +    label = g_strdup(qemu_opts_id(opts));
> +    fprintf(stderr, "char device %s redirected to %s\n", label, q_ptsname(master_fd));
>  
>      s = g_malloc0(sizeof(PtyCharDriver));
>      chr->opaque = s;

qemu_opts_id() may return null.  g_strdup() then also returns null.
Printing null with %s crashes on some systems.

You leak label.  Best fixed by not allocating in the first place.

Try this:

    label = qemu_opts_id(opts)
    fprintf(stderr, "char device%S%s redirected to %s\n",
            label ? " " : "",
            label ?: , "",
            q_ptsname(master_fd));

Don't forget to imporve your subject :)

      parent reply	other threads:[~2012-12-20 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 14:49 [Qemu-devel] [PATCH] qemu-char: inherit ptys and imporve output from -serial pty Lei Li
2012-12-20 14:58 ` Lei Li
2012-12-20 15:19 ` Markus Armbruster [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=87bodohhtg.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=lilei@linux.vnet.ibm.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.