From: Meador Inge <meadori@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: riku.voipio@iki.fi
Subject: [Qemu-devel] [RFC PATCH 0/1] linux-user: Issue running applications through ld.so
Date: Thu, 7 Jun 2012 15:59:01 -0500 [thread overview]
Message-ID: <1339102742-4584-1-git-send-email-meadori@codesourcery.com> (raw)
Hi All,
I am running into an issue where QEMU fails to map a target executable
due to hitting the lower limit on /proc/sys/vm/mmap_min_addr. This normally
just works because of all the nice guest base probing we have in place:
$ cat /proc/sys/vm/mmap_min_addr
4096
$ qemu-arm ./hello.out
Hello, World!
In cases where the executable is run through the glibc loader we are not so
lucky:
$ qemu-arm /path/to/lib/ld-2.15.so --library-path /path/to/lib/ ./hello.out
./hello.out: error while loading shared libraries: ./hello.out: failed to map
segment from shared object: Permission denied
The reason is that we successfully load the loader (since it can be put
anywhere), but later ld.so goes to map in hello.out at a fixed address
and fails because that fixed address is bellow mmap_min_addr and it is
too late to fixup the guest base.
I am able to fix the issue by probing for the guest base when needed for
shared objects. This worked for all the test cases I threw at it
(including running the gcc and glibc test suites through QEMU). However,
I am not all that familiar with the Linux usermode pieces and would like
some feedback.
Thoughts?
Meador Inge (1):
linux-user: Probe the guest base for shared objects when needed
linux-user/elfload.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-06-07 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 20:59 Meador Inge [this message]
2012-06-07 20:59 ` [Qemu-devel] [RFC PATCH 1/1] linux-user: Probe the guest base for shared objects when needed Meador Inge
2012-06-12 14:08 ` Richard Henderson
2012-06-12 18:44 ` Meador Inge
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=1339102742-4584-1-git-send-email-meadori@codesourcery.com \
--to=meadori@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).