qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tyler Hall <tylerwhall@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Tyler Hall <tylerwhall@gmail.com>
Subject: [Qemu-devel] [PATCH 1/2] exec.c: Fix off-by-one error in register_subpage
Date: Wed, 25 Jul 2012 18:45:03 -0400	[thread overview]
Message-ID: <1343256304-32029-1-git-send-email-tylerwhall@gmail.com> (raw)

subpage_register() expects "end" to be the last byte in the mapping.
Registering a non-page-aligned memory region that extends up to or
beyond a page boundary causes subpage_register() to silently fail
through the (end >= PAGE_SIZE) check.

This bug does not cause noticeable problems for mappings that do not
extend to a page boundary, though they do register an extra byte.

Signed-off-by: Tyler Hall <tylerwhall@gmail.com>
---
 exec.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exec.c b/exec.c
index feb4795..27b100c 100644
--- a/exec.c
+++ b/exec.c
@@ -2271,7 +2271,7 @@ static void register_subpage(MemoryRegionSection *section)
         subpage = container_of(existing->mr, subpage_t, iomem);
     }
     start = section->offset_within_address_space & ~TARGET_PAGE_MASK;
-    end = start + section->size;
+    end = start + section->size - 1;
     subpage_register(subpage, start, end, phys_section_add(section));
 }
 
-- 
1.7.11

             reply	other threads:[~2012-07-25 22:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 22:45 Tyler Hall [this message]
2012-07-25 22:45 ` [Qemu-devel] [PATCH 2/2] exec.c: Use subpages for large unaligned mappings Tyler Hall
2012-08-01 13:02   ` Avi Kivity
2012-08-01 10:42 ` [Qemu-devel] [Qemu-trivial] [PATCH 1/2] exec.c: Fix off-by-one error in register_subpage Stefan Hajnoczi
2012-08-01 12:52   ` Peter Maydell
2012-08-01 12:56 ` [Qemu-devel] " Avi Kivity
2012-08-01 13:01   ` Stefan Hajnoczi
2012-08-01 13:03     ` Avi Kivity
2012-08-03  9:55 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi

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=1343256304-32029-1-git-send-email-tylerwhall@gmail.com \
    --to=tylerwhall@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).