From: Marek Vasut <marex@denx.de>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vmware_vga: Redraw only visible area
Date: Fri, 17 Aug 2012 14:37:20 +0200 [thread overview]
Message-ID: <201208171437.21061.marex@denx.de> (raw)
In-Reply-To: <502E3699.701@msgid.tls.msk.ru>
Dear Michael Tokarev,
> On 17.08.2012 06:55, Marek Vasut wrote:
> > Disallow negative value boundaries of the redraw rectangle.
> > This fixes a segfault when using -vga vmware.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > ---
> >
> > hw/vmware_vga.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > NOTE: I tested this by emulating some recent version of ubuntu. The
> > rect->x
> >
> > value was set to -65 for some reason at one point, which caused the
> > kvm to crash. Trimming the rectangle fixed the issue.
> >
> > diff --git a/hw/vmware_vga.c b/hw/vmware_vga.c
> > index f5e4f44..62e5887 100644
> > --- a/hw/vmware_vga.c
> > +++ b/hw/vmware_vga.c
> > @@ -337,8 +337,8 @@ static inline void vmsvga_update_rect_delayed(struct
> > vmsvga_state_s *s,
> >
> > {
> >
> > struct vmsvga_rect_s *rect = &s->redraw_fifo[s->redraw_fifo_last
> > ++]; s->redraw_fifo_last &= REDRAW_FIFO_LEN - 1;
> >
> > - rect->x = x;
> > - rect->y = y;
> > + rect->x = (x < 0) ? 0 : x;
> > + rect->y = (y < 0) ? 0 : y;
> >
> > rect->w = w;
> > rect->h = h;
> >
> > }
>
> Is it the same as https://bugs.launchpad.net/bugs/918791 ?
> At least it appears to be the same theme... But there,
> the patch (https://launchpadlibrarian.net/94916786/qemu-vmware.debdiff)
> also updates width/height. My comment:
> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/918791/comments/21
Looks to be the same ... though my patch tries to squash the issue as early as
possible.
You're right that x and y might overflow to the other side too. Also, you're
right about w and h.
Shall I send updated patch?
> "So indeed, some (upstream) verification is needed here -- where these
> negative values are coming from, whenever it is EVER okay to have them,
> what to do with these, and where to check (I guess the check should be
> done somewhere in the upper layer)."
>
> Especially the last part about the layer.
Where's the upper layer though, isn't that what's pouring out of the virtual
machine itself?
> Thanks,
Thank you for guidance !
> /mjt
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-08-17 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 2:55 [Qemu-devel] [PATCH] vmware_vga: Redraw only visible area Marek Vasut
2012-08-17 12:18 ` Michael Tokarev
2012-08-17 12:37 ` Marek Vasut [this message]
2012-09-16 20:36 ` Marek Vasut
2012-09-17 4:52 ` Michael Tokarev
2012-09-17 10:15 ` Marek Vasut
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=201208171437.21061.marex@denx.de \
--to=marex@denx.de \
--cc=mjt@tls.msk.ru \
--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).