qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: pyssling@ludd.ltu.se, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-char: Fix missed data on unix socket
Date: Mon, 13 Jul 2015 12:15:22 +0200	[thread overview]
Message-ID: <55A38FBA.50505@redhat.com> (raw)
In-Reply-To: <1436775182-67309-1-git-send-email-pyssling@ludd.ltu.se>



On 13/07/2015 10:13, pyssling@ludd.ltu.se wrote:
> Commit 812c1057 introduced HUP detection on unix and tcp sockets prior
> to a read in tcp_chr_read. This unfortunately broke CloudStack 4.2
> which relied on the old behaviour where data on a socket was readable
> even if a HUP was present.
> 
> On Linux a working solution seems to be to simply check the HUP after
> reading available data, while keeping the original behaviour for windows.
> 
> There is then a divergence in behaviour for the two platforms, but this
> seems better than breaking a whole software stack.

There is no need to do something special on Windows, I think.  You can
unconditionally check G_IO_HUP after reading.  One nit:

> -    if (size == 0) {
> +    if (size == 0 || (size < 0 && cond & G_IO_HUP)) {

Please put (cond & G_IO_HUP) within parentheses.

Please

  reply	other threads:[~2015-07-13 10:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  8:13 [Qemu-devel] [PATCH] qemu-char: Fix missed data on unix socket pyssling
2015-07-13 10:15 ` Paolo Bonzini [this message]
2015-07-13 10:41   ` Amit Shah
2015-07-13 13:15     ` Nils Carlson
2015-07-15 21:44       ` Nils Carlson
2015-07-16  6:24         ` Amit Shah
2015-07-16  8:11           ` Nils Carlson
2015-07-16 11:19             ` Amit Shah

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=55A38FBA.50505@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=pyssling@ludd.ltu.se \
    --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).