From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vnc_refresh: calling vnc_update_client might free vs
Date: Tue, 26 Jan 2010 18:07:14 -0600 [thread overview]
Message-ID: <4B5F83B2.8060003@codemonkey.ws> (raw)
In-Reply-To: <alpine.DEB.2.00.1001251210570.7512@kaball-desktop>
On 01/25/2010 06:54 AM, Stefano Stabellini wrote:
> Hi all,
> this patch fixes another bug in vnc_refresh: calling vnc_update_client
> might cause vs to be free()ed, in this case we cannot access vs->next
> right after to examine the next item on the list.
>
> Signed-off-by: Stefano Stabellini<stefano.stabellini@eu.citrix.com>
>
Applied. Thanks.
Regards,
Anthony Liguori
> ---
>
> diff --git a/vnc.c b/vnc.c
> index cc2a26e..92facde 100644
> --- a/vnc.c
> +++ b/vnc.c
> @@ -2345,7 +2345,7 @@ static int vnc_refresh_server_surface(VncDisplay *vd)
> static void vnc_refresh(void *opaque)
> {
> VncDisplay *vd = opaque;
> - VncState *vs = NULL;
> + VncState *vs = NULL, *vn = NULL;
> int has_dirty = 0, rects = 0;
>
> vga_hw_update();
> @@ -2354,8 +2354,10 @@ static void vnc_refresh(void *opaque)
>
> vs = vd->clients;
> while (vs != NULL) {
> + vn = vs->next;
> rects += vnc_update_client(vs, has_dirty);
> - vs = vs->next;
> + /* vs might be free()ed here */
> + vs = vn;
> }
> /* vd->timer could be NULL now if the last client disconnected,
> * in this case don't update the timer */
>
>
>
>
next prev parent reply other threads:[~2010-01-27 0:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 12:54 [Qemu-devel] [PATCH] vnc_refresh: calling vnc_update_client might free vs Stefano Stabellini
2010-01-27 0:07 ` Anthony Liguori [this message]
2010-01-27 9:53 ` Gerd Hoffmann
2010-01-27 12:29 ` Stefano Stabellini
2010-01-27 14:08 ` Anthony Liguori
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=4B5F83B2.8060003@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
/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).