qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: qemu-devel@nongnu.org, "Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] io: fix handling of EOF / error conditions in websock GSource
Date: Thu, 21 Feb 2019 09:28:41 +0000	[thread overview]
Message-ID: <20190221092841.GC17899@redhat.com> (raw)
In-Reply-To: <f304df7c-e0ba-042d-4ef7-d6492cb77569@redhat.com>

On Wed, Feb 20, 2019 at 08:52:34PM +0100, Philippe Mathieu-Daudé wrote:
> Hi Daniel,
> 
> On 2/20/19 7:25 PM, Daniel P. Berrangé wrote:
> > We were never reporting the G_IO_HUP event when an end of file was hit
> > on the websocket channel.
> > 
> > We also ddn't report G_IO_ERR when we hit a fatal error processing the
> 
> "didn't report"
> 
> > websocket protocol.
> > 
> > The latter in particular meant that the chardev code would not notice
> > when an eof/error was encountered on the websocket channel, unless the
> > guest OS happened to trigger a write operation.
> > 
> > This meant that once the first client had quit, the chardev would never
> > listen to accept a new client.
> > 
> > Fixes launchpad bug 1816819
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> >  io/channel-websock.c | 8 +++++++-
> >  1 file changed, 7 insertions(+), 1 deletion(-)
> > 
> > diff --git a/io/channel-websock.c b/io/channel-websock.c
> > index dc43dc6bb9..fc4c3dcaa5 100644
> > --- a/io/channel-websock.c
> > +++ b/io/channel-websock.c
> > @@ -1225,12 +1225,18 @@ qio_channel_websock_source_check(GSource *source)
> >      QIOChannelWebsockSource *wsource = (QIOChannelWebsockSource *)source;
> >      GIOCondition cond = 0;
> >  
> > -    if (wsource->wioc->rawinput.offset || wsource->wioc->io_eof) {
> > +    if (wsource->wioc->rawinput.offset) {
> >          cond |= G_IO_IN;
> >      }
> >      if (wsource->wioc->encoutput.offset < QIO_CHANNEL_WEBSOCK_MAX_BUFFER) {
> >          cond |= G_IO_OUT;
> >      }
> > +    if (wsource->wioc->io_eof) {
> > +        cond |= G_IO_IN | G_IO_HUP;
> 
> Shouldn't this be:
> 
>            cond |= G_IO_HUP;

With regular poll() on FD I believe you typically get POLLIN | POLLHUP as
a pair.

> 
> > +    }
> > +    if (wsource->wioc->io_err) {
> > +        cond |= G_IO_IN | G_IO_ERR;
> 
> Ditto:
> 
>            cond |= G_IO_ERR;

And I just followed the same practice here.

> > +    }
> >  
> >      return cond & wsource->condition;

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

      reply	other threads:[~2019-02-21  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 18:25 [Qemu-devel] [PATCH] io: fix handling of EOF / error conditions in websock GSource Daniel P. Berrangé
2019-02-20 19:52 ` Philippe Mathieu-Daudé
2019-02-21  9:28   ` Daniel P. Berrangé [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=20190221092841.GC17899@redhat.com \
    --to=berrange@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=philmd@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).