From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
"Daniel P. Berrange" <berrange@redhat.com>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH v2] vnc: do not disconnect on EAGAIN
Date: Mon, 06 Feb 2017 15:26:03 +0100 [thread overview]
Message-ID: <1486391163.32329.24.camel@redhat.com> (raw)
In-Reply-To: <1486115549-9398-1-git-send-email-mjt@msgid.tls.msk.ru>
On Fr, 2017-02-03 at 12:52 +0300, Michael Tokarev wrote:
> When qemu vnc server is trying to send large update to clients,
> there might be a situation when system responds with something
> like EAGAIN, indicating that there's no system memory to send
> that much data (depending on the network speed, client and server
> and what is happening). In this case, something like this happens
> on qemu side (from strace):
>
> sendmsg(16, {msg_name(0)=NULL,
> msg_iov(1)=[{"\244\"..., 729186}],
> msg_controllen=0, msg_flags=0}, 0) = 103950
> sendmsg(16, {msg_name(0)=NULL,
> msg_iov(1)=[{"lz\346"..., 1559618}],
> msg_controllen=0, msg_flags=0}, 0) = -1 EAGAIN
> sendmsg(-1, {msg_name(0)=NULL,
> msg_iov(1)=[{"lz\346"..., 1559618}],
> msg_controllen=0, msg_flags=0}, 0) = -1 EBADF
>
> qemu closes the socket before the retry, and obviously it gets EBADF
> when trying to send to -1.
>
> This is because there WAS a special handling for EAGAIN, but now it doesn't
> work anymore, after commit 04d2529da27db512dcbd5e99d0e26d333f16efcc, because
> now in all error-like cases we initiate vnc disconnect.
>
> This change were introduced in qemu 2.6, and caused numerous grief for many
> people, resulting in their vnc clients reporting sporadic random disconnects
> from vnc server.
>
> Fix that by doing the disconnect only when necessary, i.e. omitting this
> very case of EAGAIN.
>
> Hopefully the existing condition (comparing with QIO_CHANNEL_ERR_BLOCK)
> is sufficient, as the original code (before the above commit) were
> checking for other errno values too.
>
> Apparently there's another (semi?)bug exist somewhere here, since the
> code tries to write to fd# -1, it probably should check if the connection
> is open before. But this isn't important.
>
> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
> Fixes: 04d2529da27db512dcbd5e99d0e26d333f16efcc
> Cc: Daniel P. Berrange <berrange@redhat.com>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: qemu-stable@nongnu.org
Added to ui patch queue.
thanks,
Gerd
prev parent reply other threads:[~2017-02-06 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 9:52 [Qemu-trivial] [PATCH v2] vnc: do not disconnect on EAGAIN Michael Tokarev
2017-02-03 10:07 ` Daniel P. Berrange
2017-02-06 14:26 ` Gerd Hoffmann [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=1486391163.32329.24.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=berrange@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=qemu-trivial@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).