From: Laszlo Ersek <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Li Qiang <liq3ea@gmail.com>,
qemu-devel@nongnu.org, ghoffman@redhat.com, liqiang6-s@360.cn
Subject: Re: [Qemu-devel] [PATCH] cirrus: fix oob access issue
Date: Tue, 24 Jan 2017 12:24:49 +0100 [thread overview]
Message-ID: <a513396f-fbe3-1e03-df83-04c0c6143ace@redhat.com> (raw)
In-Reply-To: <b269fc2b-e211-cc70-0b7e-da6b3180df88@redhat.com>
On 01/24/17 12:17, Laszlo Ersek wrote:
> On 01/24/17 11:48, Gerd Hoffmann wrote:
>>>> diff --git a/hw/display/cirrus_vga.c b/hw/display/cirrus_vga.c
>>>> index 379910d..7ddd289 100644
>>>> --- a/hw/display/cirrus_vga.c
>>>> +++ b/hw/display/cirrus_vga.c
>>>> @@ -277,7 +277,8 @@ static bool blit_region_is_unsafe(struct CirrusVGAState *s,
>>>> }
>>>> if (pitch < 0) {
>>>> int64_t min = addr
>>>> - + ((int64_t)s->cirrus_blt_height-1) * pitch;
>>>> + + ((int64_t)s->cirrus_blt_height-1) * pitch
>>>> + - s->cirrus_blt_width;
>>>> int32_t max = addr
>>>> + s->cirrus_blt_width;
>>>> if (min < 0 || max > s->vga.vram_size) {
>>>>
>>>
>>> I believe this is incorrect. In this case (AFAIR), "addr" points to the
>>> left-most pixel (= lowest address) of the bottom line (= highest
>>> address).
>>
>> If I read the code correctly it is backwards *both* x and y axis, so
>> addr is the right-most pixel of the bottom line.
>
> What is "max" then? If "addr" is the right-most pixel of the bottom
> line, then "max" has the highest address just past the rectangle, and
> then adding anything non-negative to it makes no sense.
sorry, over-editing caused a bug. I meant
If "addr" is the right-most pixel of the bottom line (or just one
past that), then *it* has the highest address, and then adding
anything non-negative to it (i.e., how we end up with "max") makes no
sense.
I should have started with the diagram, not with the text.
Thanks
Laszlo
>
> Adding a negative value to it (i.e., if s->cirrus_blt_width were
> negative) might make sense, for getting the leftmost pixel on the bottom
> line, but then that "max" value shouldn't be used for the final boundary
> check (against RAM size).
>
> ... Really as I remember it from the downstream review, the pitch is
> negative (bottom-up), but the horizontal direction remains left to right.
>
> 0-----------------------------------------------------------------> x
> |
> | addr + (height - 1) * pitch, pitch < 0, height > 0
> | |
> | v
> | *--------------------* <-- addr + (height - 1) * pitch + width
> | | |
> | | |
> | | |
> | | |
> | | |
> | | |
> | *--------------------*
> | ^ ^
> | | |
> | addr max = addr + width, width > 0
> |
> v
> y
>
>
> The rightmost column represented here is exclusive, the rest is inclusive.
>
> Thanks
> Laszlo
>
next prev parent reply other threads:[~2017-01-24 11:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 9:34 [Qemu-devel] [PATCH] cirrus: fix oob access issue Li Qiang
2017-01-24 9:50 ` no-reply
2017-01-24 10:23 ` Laszlo Ersek
2017-01-24 10:48 ` Gerd Hoffmann
2017-01-24 11:17 ` Laszlo Ersek
2017-01-24 11:24 ` Laszlo Ersek [this message]
2017-01-24 12:29 ` Gerd Hoffmann
2017-01-24 15:31 ` Wolfgang Bumiller
2017-01-24 16:12 ` Laszlo Ersek
2017-01-25 1:18 ` Li Qiang
2017-01-25 3:31 ` Laszlo Ersek
2017-01-25 7:26 ` Gerd Hoffmann
2017-01-25 7:18 ` Gerd Hoffmann
2017-01-25 10:13 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2017-01-24 9:58 Li Qiang
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=a513396f-fbe3-1e03-df83-04c0c6143ace@redhat.com \
--to=lersek@redhat.com \
--cc=ghoffman@redhat.com \
--cc=kraxel@redhat.com \
--cc=liq3ea@gmail.com \
--cc=liqiang6-s@360.cn \
--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).