From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: yhalperi@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/qxl: guest bug on primary create with stride %4 != 0
Date: Wed, 17 Oct 2012 15:42:40 +0200 [thread overview]
Message-ID: <507EB5D0.7000706@redhat.com> (raw)
In-Reply-To: <1350305643-31096-1-git-send-email-alevy@redhat.com>
On 10/15/12 14:54, Alon Levy wrote:
> Due to usage of pixman for rendering on all spice surfaces we have
> pixman's requirement that the stride be word aligned. A guest not
> honoring that can crash spice and qemu with it due to failure to create
> a surface (in spice-server). Avoid this early on in primary surface
> creation and offscreen surface creation.
Patch added to spice patch queue.
thanks,
Gerd
prev parent reply other threads:[~2012-10-17 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 12:54 [Qemu-devel] [PATCH] hw/qxl: guest bug on primary create with stride %4 != 0 Alon Levy
2012-10-17 13:42 ` Gerd Hoffmann [this message]
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=507EB5D0.7000706@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yhalperi@redhat.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).