From: Laszlo Ersek <lersek@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] cirrus_vga: fix off-by-one in blit_region_is_unsafe
Date: Wed, 10 Feb 2016 17:54:00 +0100 [thread overview]
Message-ID: <56BB6B28.9030605@redhat.com> (raw)
In-Reply-To: <1455121059-18280-1-git-send-email-pbonzini@redhat.com>
On 02/10/16 17:17, Paolo Bonzini wrote:
> The "max" value is being compared with >=, but addr + width points to
> the first byte that will _not_ be copied. Laszlo suggested using a
> "greater than" comparison, instead of subtracting one like it is
> already done above for the height, so that max remains always positive.
>
> The mistake is "safe"---it will reject some blits, but will never cause
> out-of-bounds writes.
>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> hw/display/cirrus_vga.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/display/cirrus_vga.c b/hw/display/cirrus_vga.c
> index b6ce1c8..57b91a7 100644
> --- a/hw/display/cirrus_vga.c
> +++ b/hw/display/cirrus_vga.c
> @@ -276,14 +276,14 @@ static bool blit_region_is_unsafe(struct CirrusVGAState *s,
> + ((int64_t)s->cirrus_blt_height-1) * pitch;
> int32_t max = addr
> + s->cirrus_blt_width;
> - if (min < 0 || max >= s->vga.vram_size) {
> + if (min < 0 || max > s->vga.vram_size) {
> return true;
> }
> } else {
> int64_t max = addr
> + ((int64_t)s->cirrus_blt_height-1) * pitch
> + s->cirrus_blt_width;
> - if (max >= s->vga.vram_size) {
> + if (max > s->vga.vram_size) {
> return true;
> }
> }
>
Thank you for your patience. :)
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
next prev parent reply other threads:[~2016-02-10 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 16:17 [Qemu-devel] [PATCH v2] cirrus_vga: fix off-by-one in blit_region_is_unsafe Paolo Bonzini
2016-02-10 16:54 ` Laszlo Ersek [this message]
2016-02-16 13:30 ` Gerd Hoffmann
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=56BB6B28.9030605@redhat.com \
--to=lersek@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@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).