From: Anthony Liguori <anthony@codemonkey.ws>
To: Roland Dreier <rdreier@cisco.com>
Cc: Dave Airlie <airlied@gmail.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH to consider for 0.12] vmware_vga: Don't crash on too-big DEFINE_CURSOR command
Date: Thu, 17 Dec 2009 16:48:41 -0600 [thread overview]
Message-ID: <4B2AB549.7090209@codemonkey.ws> (raw)
In-Reply-To: <adaljh1441g.fsf@roland-alpha.cisco.com>
Roland Dreier wrote:
> > His last patch has the same fix without the printf(). The printf is
> > probably something to avoid since a malicious guest could create a
> > storm of them. Since libvirt logs stderr by default, the result could
> > be pretty nasty.
>
> By the way, are the
>
> fprintf(stderr, "%s: update width too large x: %d, w: %d\n",
> __FUNCTION__, x, w);
>
> fprintf(stderr, "%s: update height too large y: %d, h: %d\n",
> __FUNCTION__, y, h);
>
> prints triggerable by a guest? (I think so -- if so I can send a patch
> removing them if you want)
>
> How about the printf()s to stdout? eg a guest can cause a flood of the
>
> printf("%s: Unknown command 0x%02x in SVGA command FIFO\n",
> __FUNCTION__, cmd);
>
> or
>
> printf("%s: guest runs %s.\n", __FUNCTION__,
> vmsvga_guest_id[value - GUEST_OS_BASE]);
>
> output if it wants pretty trivially.
>
Yeah, that's all stuff that needs to go.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-12-17 22:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 22:27 [Qemu-devel] [PATCH to consider for 0.12] vmware_vga: Don't crash on too-big DEFINE_CURSOR command Roland Dreier
2009-12-17 22:34 ` [Qemu-devel] " Anthony Liguori
2009-12-17 22:38 ` Roland Dreier
2009-12-17 22:49 ` Anthony Liguori
2009-12-17 22:41 ` Roland Dreier
2009-12-17 22:48 ` Anthony Liguori [this message]
2009-12-20 18:06 ` Roland Dreier
2010-01-06 4:43 ` [Qemu-devel] [PATCH resend] vmware_vga: Check cursor dimensions passed from guest to avoid buffer overflow Roland Dreier
2010-01-11 16:01 ` 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=4B2AB549.7090209@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=airlied@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rdreier@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.