From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Klim Kireev <klim.kireev@virtuozzo.com>
Cc: qemu-devel@nongnu.org, den@virtuozzo.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH] vnc: fix segfault in closed connection handling
Date: Wed, 14 Feb 2018 15:21:37 +0000 [thread overview]
Message-ID: <20180214152137.GG5171@redhat.com> (raw)
In-Reply-To: <20180207094844.21402-1-klim.kireev@virtuozzo.com>
On Wed, Feb 07, 2018 at 12:48:44PM +0300, Klim Kireev wrote:
> On one of our client's node, due to trying to read from closed ioc,
> a segmentation fault occured. Corresponding backtrace:
>
> 0 object_get_class (obj=obj@entry=0x0)
> 1 qio_channel_readv_full (ioc=0x0, iov=0x7ffe55277180 ...
> 2 qio_channel_read (ioc=<optimized out> ...
> 3 vnc_client_read_buf (vs=vs@entry=0x55625f3c6000, ...
> 4 vnc_client_read_plain (vs=0x55625f3c6000)
> 5 vnc_client_read (vs=0x55625f3c6000)
> 6 vnc_client_io (ioc=<optimized out>, condition=G_IO_IN, ...
> 7 g_main_dispatch (context=0x556251568a50)
> 8 g_main_context_dispatch (context=context@entry=0x556251568a50)
> 9 glib_pollfds_poll ()
> 10 os_host_main_loop_wait (timeout=<optimized out>)
> 11 main_loop_wait (nonblocking=nonblocking@entry=0)
> 12 main_loop () at vl.c:1909
> 13 main (argc=<optimized out>, argv=<optimized out>, ...
>
> Having analyzed the coredump, I understood that the reason is that
> ioc_tag is reset on vnc_disconnect_start and ioc is cleaned
> in vnc_disconnect_finish. Between these two events due to some
> reasons the ioc_tag was set again and after vnc_disconnect_finish
> the handler is running with freed ioc,
> which led to the segmentation fault.
>
> The patch checks vs->disconnecting in places where we call
> qio_channel_add_watch and resets handler if disconnecting == TRUE
> to prevent such an occurrence.
>
> Signed-off-by: Klim Kireev <klim.kireev@virtuozzo.com>
> ---
> Changelog:
> v2: Attach the backtrace
>
> v3: Change checks
>
> ui/vnc-jobs.c | 6 ++++--
> ui/vnc.c | 15 ++++++++++++++-
> 2 files changed, 18 insertions(+), 3 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>
> diff --git a/ui/vnc-jobs.c b/ui/vnc-jobs.c
> index e326679dd0..868dddef4b 100644
> --- a/ui/vnc-jobs.c
> +++ b/ui/vnc-jobs.c
> @@ -148,8 +148,10 @@ void vnc_jobs_consume_buffer(VncState *vs)
> if (vs->ioc_tag) {
> g_source_remove(vs->ioc_tag);
> }
> - vs->ioc_tag = qio_channel_add_watch(
> - vs->ioc, G_IO_IN | G_IO_OUT, vnc_client_io, vs, NULL);
> + if (vs->disconnecting == FALSE) {
> + vs->ioc_tag = qio_channel_add_watch(
> + vs->ioc, G_IO_IN | G_IO_OUT, vnc_client_io, vs, NULL);
> + }
> }
> buffer_move(&vs->output, &vs->jobs_buffer);
>
> diff --git a/ui/vnc.c b/ui/vnc.c
> index 93731accb6..67ccc8160f 100644
> --- a/ui/vnc.c
> +++ b/ui/vnc.c
> @@ -1536,12 +1536,19 @@ gboolean vnc_client_io(QIOChannel *ioc G_GNUC_UNUSED,
> VncState *vs = opaque;
> if (condition & G_IO_IN) {
> if (vnc_client_read(vs) < 0) {
> - return TRUE;
> + goto end;
> }
> }
> if (condition & G_IO_OUT) {
> vnc_client_write(vs);
> }
> +end:
> + if (vs->disconnecting) {
> + if (vs->ioc_tag != 0) {
> + g_source_remove(vs->ioc_tag);
> + }
> + vs->ioc_tag = 0;
> + }
> return TRUE;
> }
>
> @@ -1630,6 +1637,12 @@ void vnc_flush(VncState *vs)
> if (vs->ioc != NULL && vs->output.offset) {
> vnc_client_write_locked(vs);
> }
> + if (vs->disconnecting) {
> + if (vs->ioc_tag != 0) {
> + g_source_remove(vs->ioc_tag);
> + }
> + vs->ioc_tag = 0;
> + }
> vnc_unlock_output(vs);
> }
>
> --
> 2.14.3
>
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 :|
next prev parent reply other threads:[~2018-02-14 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 9:48 [Qemu-devel] [PATCH] vnc: fix segfault in closed connection handling Klim Kireev
2018-02-14 14:43 ` [Qemu-devel] [PATCH v3] " Klim Kireev
2018-02-16 11:25 ` Gerd Hoffmann
2018-02-14 15:21 ` Daniel P. Berrangé [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-31 13:06 [Qemu-devel] [PATCH] " Klim Kireev
2018-01-31 13:16 ` Marc-André Lureau
2018-01-31 13:18 ` klim
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=20180214152137.GG5171@redhat.com \
--to=berrange@redhat.com \
--cc=den@virtuozzo.com \
--cc=klim.kireev@virtuozzo.com \
--cc=kraxel@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).