From: Tim Hardeck <thardeck@suse.de>
To: qemu-devel@nongnu.org
Cc: Tim Hardeck <thardeck@suse.de>, aliguori@us.ibm.com
Subject: [Qemu-devel] [PATCH 0/2] fix segfaults triggered by failed vnc handshakes
Date: Tue, 9 Oct 2012 17:21:39 +0200 [thread overview]
Message-ID: <1349796101-6660-1-git-send-email-thardeck@suse.de> (raw)
While trying to adapt Anthony Liguori's websockets patches to the current standard I ran into some segfaults.
They were triggered during disconnects due to failed VNC handshakes.
I have added checks to prevent them.
Tim Hardeck (2):
vnc: fix segfault due to failed handshake
qemu queue: fix uninitialized removals
qemu-queue.h | 8 ++++++--
ui/vnc.c | 4 +++-
2 files changed, 9 insertions(+), 3 deletions(-)
--
1.7.10.4
next reply other threads:[~2012-10-09 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 15:21 Tim Hardeck [this message]
2012-10-09 15:21 ` [Qemu-devel] [PATCH 1/2] vnc: fix segfault due to failed handshake Tim Hardeck
2012-10-09 15:21 ` [Qemu-devel] [PATCH 2/2] qemu queue: fix uninitialized removals Tim Hardeck
-- strict thread matches above, loose matches on Subject: below --
2012-10-14 13:08 [Qemu-devel] [PATCH 0/2] fix segfaults triggered by failed vnc handshakes Tim Hardeck
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=1349796101-6660-1-git-send-email-thardeck@suse.de \
--to=thardeck@suse.de \
--cc=aliguori@us.ibm.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).