From: David Gibson <david@gibson.dropbear.id.au>
To: Avi Kivity <avi@redhat.com>,
agraf@suse.de, anthony@codemonkey.ws, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix subtle integer overflow bug in memory API
Date: Thu, 15 Sep 2011 12:58:03 +1000 [thread overview]
Message-ID: <20110915025803.GP9025@yookeroo.fritz.box> (raw)
In-Reply-To: <20110915023431.GO9025@yookeroo.fritz.box>
On Thu, Sep 15, 2011 at 12:34:31PM +1000, David Gibson wrote:
> On Wed, Sep 14, 2011 at 11:23:25AM +0300, Avi Kivity wrote:
> > On 09/14/2011 10:02 AM, David Gibson wrote:
> > >It is quite common to have a MemoryRegion with size of INT64_MAX.
> > >When processing alias regions in render_memory_region() it's quite
> > >easy to find a case where it will construct a temporary AddrRange with
> > >a non-zero start, and size still of INT64_MAX. When means attempting
> > >to compute the end of such a range as start + size will result in
> > >signed integer overflow.
> > >
> > >This integer overflow means that addrrange_intersects() can
> > >incorrectly report regions as not intersecting when they do. For
> > >example consider the case of address ranges {0x10000000000,
> > >0x7fffffffffffffff} and {0x10010000000, 0x10000000} where the second
> > >is in fact included completely in the first.
> >
> > Good catch, thanks for digging this out.
> >
> > >This patch rearranges addrrange_intersects() to avoid the integer
> > >overflow, correcting this behaviour.
> >
> > I expect that the bad behaviour can still be triggered, for example
> > by pointing aliases towards the end of very large regions. Not that
> > I expect this to occur in practice.
>
> Well.. I'm pretty sure that particular case can no longer be
> triggered. But there may be other integer overflow bugs in this code,
> though I didn't spot them at a glance.
Actually, there definitely are. addrrange_end() should probably be
redefined as the inclusive end, rather than the exclusive end, and
computed as:
(start + size - 1) < start ? INT64_MAX : start + size - 1
Hrm, except that that doesn't handle zero size ranges. And gets a bit
weird for INT64_MAX sized regions.
Hrm, yeah, these really should be changed to use unsigneds.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2011-09-15 2:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 7:02 [Qemu-devel] [PATCH] Fix subtle integer overflow bug in memory API David Gibson
2011-09-14 8:23 ` Avi Kivity
2011-09-14 8:38 ` Avi Kivity
2011-09-15 2:34 ` David Gibson
2011-09-15 2:58 ` David Gibson [this message]
2011-09-15 7:28 ` Avi Kivity
2011-09-16 3:16 ` David Gibson
2011-09-15 7:38 ` Paolo Bonzini
2011-09-15 7:43 ` Avi Kivity
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=20110915025803.GP9025@yookeroo.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@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).