qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vince Weaver <vince@csl.cornell.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] another 64/32 mmap() bug
Date: Sat, 27 Sep 2008 18:28:30 -0400 (EDT)	[thread overview]
Message-ID: <20080927182454.A29159@stanley.csl.cornell.edu> (raw)


In trying to get the remaining spec2k/spec2k6 benchmarks to run, I've 
found another 64-bit/32-bit mmap() linux-user problem.

This could be a kernel problem.

The mmap() call in conjunction with MAP_32BIT will make sure the address 
of an allocation is < 32-bit.  The problem is it doesn't check that the
_entire address range_ is < 32-bit.

So it will return an address of say 0xffff0000 for an allocation of
128kB, and the end of that allocation will not be addressable, causing 
a segfault.

Vince

             reply	other threads:[~2008-09-27 22:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-27 22:28 Vince Weaver [this message]
2008-09-28 19:11 ` [Qemu-devel] another 64/32 mmap() bug Vince Weaver

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=20080927182454.A29159@stanley.csl.cornell.edu \
    --to=vince@csl.cornell.edu \
    --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).