From: Edgar Kaziakhmedov <edgar.kaziakhmedov@virtuozzo.com>
To: "Denis V. Lunev" <den@openvz.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] io/channel-websock: handle continuous reads without any data
Date: Wed, 10 Jan 2018 12:55:19 +0300 [thread overview]
Message-ID: <01f897dd-9b76-cdda-52ec-b4164ef8179f@virtuozzo.com> (raw)
In-Reply-To: <1514453778-5363-1-git-send-email-den@openvz.org>
ping
On 12/28/2017 12:36 PM, Denis V. Lunev wrote:
> From: Edgar Kaziakhmedov <edgar.kaziakhmedov@virtuozzo.com>
>
> According to the current implementation of websocket protocol in QEMU,
> qio_channel_websock_handshake_io tries to read handshake from the
> channel to start communication over tcp socket. But this subroutine
> doesn't cover scenario when socket was closed while handshaking. Therefore,
> if G_IO_IN is caught and qio_channel_websock_handshake_read returns
> zero, error has to be set and connection has to be done.
>
> Such behaviour causes 100% CPU load in main QEMU loop, because main loop
> poll continues to receive and handle G_IO_IN events from websocket.
>
> Step to reproduce 100% CPU load:
> - start qemu with the simplest configuration
> $ qemu -vnc [::1]:1,websocket=7500
> 2) open any vnc listener (which doesn't follow websocket protocol)
> $ vncviewer :7500
> 3) kill listener
> 4) qemu main thread eats 100% CPU usage
>
> Signed-off-by: Edgar Kaziakhmedov <edgar.kaziakhmedov@virtuozzo.com>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Daniel P. Berrange <berrange@redhat.com>
> ---
> io/channel-websock.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/io/channel-websock.c b/io/channel-websock.c
> index 87ebdeb..71f046a 100644
> --- a/io/channel-websock.c
> +++ b/io/channel-websock.c
> @@ -581,9 +581,11 @@ static gboolean qio_channel_websock_handshake_io(QIOChannel *ioc,
> return FALSE;
> }
> if (ret == 0) {
> - trace_qio_channel_websock_handshake_pending(ioc, G_IO_IN);
> - /* need more data still */
> - return TRUE;
> + /* If G_IN_IO happened and there is no data to read, close connection */
> + error_setg(&err, "connection was closed");
> + qio_task_set_error(task, err);
> + qio_task_complete(task);
> + return FALSE;
> }
>
> if (err) {
next prev parent reply other threads:[~2018-01-10 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 9:36 [Qemu-devel] [PATCH 1/1] io/channel-websock: handle continuous reads without any data Denis V. Lunev
2018-01-10 9:55 ` Edgar Kaziakhmedov [this message]
2018-01-10 12:33 ` Daniel P. Berrange
2018-01-10 13:31 ` Edgar Kaziakhmedov
2018-01-10 13:34 ` Daniel P. Berrange
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=01f897dd-9b76-cdda-52ec-b4164ef8179f@virtuozzo.com \
--to=edgar.kaziakhmedov@virtuozzo.com \
--cc=den@openvz.org \
--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).