From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 0/2] vnc patch queue
Date: Tue, 1 Jul 2014 13:33:59 +0200 [thread overview]
Message-ID: <1404214441-5106-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Carrying two bugfixes.
please pull,
Gerd
The following changes since commit b3959efdbb2dc3d5959e3b0a8e188126930beca8:
Merge remote-tracking branch 'remotes/afaerber/tags/qom-devices-for-2.1' into staging (2014-07-01 11:00:53 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-vnc-20140701-1
for you to fetch changes up to bea60dd7679364493a0d7f5b54316c767cf894ef:
ui/vnc: fix potential memory corruption issues (2014-07-01 13:26:40 +0200)
----------------------------------------------------------------
vnc: two bugfixes (by Peter Lieven).
----------------------------------------------------------------
Peter Lieven (2):
ui/vnc: limit client_cut_text msg payload size
ui/vnc: fix potential memory corruption issues
ui/vnc.c | 162 +++++++++++++++++++++++++++++++--------------------------------
ui/vnc.h | 14 +++---
2 files changed, 87 insertions(+), 89 deletions(-)
next reply other threads:[~2014-07-01 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 11:33 Gerd Hoffmann [this message]
2014-07-01 11:34 ` [Qemu-devel] [PULL 1/2] ui/vnc: limit client_cut_text msg payload size Gerd Hoffmann
2014-07-01 11:34 ` [Qemu-devel] [PULL 2/2] ui/vnc: fix potential memory corruption issues Gerd Hoffmann
2014-07-01 15:16 ` [Qemu-devel] [PULL 0/2] vnc patch queue Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2014-09-18 6:33 Gerd Hoffmann
2014-09-18 18:30 ` Peter Maydell
2014-10-28 10:59 Gerd Hoffmann
2014-10-30 19:11 ` Peter Maydell
2014-12-10 9:32 Gerd Hoffmann
2014-12-11 11:40 ` Peter Maydell
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=1404214441-5106-1-git-send-email-kraxel@redhat.com \
--to=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).