From: "Richard W.M. Jones" <rjones@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org,
Lei Li <lilei@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] socket: don't attempt to reconnect a TCP socket in server mode
Date: Wed, 12 Sep 2012 19:34:35 +0100 [thread overview]
Message-ID: <20120912183435.GC9668@rhmail.home.annexia.org> (raw)
In-Reply-To: <1346871696-8150-1-git-send-email-aliguori@us.ibm.com>
On Wed, Sep 05, 2012 at 02:01:36PM -0500, Anthony Liguori wrote:
> Commit c3767ed0eb5d0bb25fe409ae5dec06e3411ff1b6 introduced a possible SEGV when
> using a socket chardev with server=on because it assumes that all TCP sockets
> are in client mode.
>
> This patch adds a check to only reconnect when in client mode.
>
> Cc: Lei Li <lilei@linux.vnet.ibm.com>
> Reported-by: Michael Roth <mdroth@linux.vnet.ibm.com>
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> ---
> qemu-char.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/qemu-char.c b/qemu-char.c
> index 398baf1..767da93 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -2148,10 +2148,12 @@ static int tcp_chr_write(CharDriverState *chr, const uint8_t *buf, int len)
> TCPCharDriver *s = chr->opaque;
> if (s->connected) {
> return send_all(s->fd, buf, len);
> - } else {
> + } else if (s->listen_fd == -1) {
> /* (Re-)connect for unconnected writing */
> tcp_chr_connect(chr);
> return 0;
> + } else {
> + return len;
> }
> }
Hi Anthony,
I just came around this patch when I was trying to fix this
bug: https://bugzilla.redhat.com/show_bug.cgi?id=853408
qemu segfaults when trying to write to a serial socket which
is *not* a server socket and has been closed by the other end.
Unfortunately your patch above does not fix it. Only a
complete revert of c3767ed0eb5d0 fixes it.
I don't understand the purpose of c3767ed0eb5d0 at all. It
seems to set the s->connected flag and carries on regardless,
happily calling write (-1, ...), which is completely broken.
The other end closed the socket. There's no one listening on the
other end, and setting the s->connected flag will not help that.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
next prev parent reply other threads:[~2012-09-12 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 19:01 [Qemu-devel] [PATCH] socket: don't attempt to reconnect a TCP socket in server mode Anthony Liguori
2012-09-12 18:34 ` Richard W.M. Jones [this message]
2012-09-12 19:37 ` Anthony Liguori
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=20120912183435.GC9668@rhmail.home.annexia.org \
--to=rjones@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=lilei@linux.vnet.ibm.com \
--cc=pbonzini@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 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).