From: "John Z. Bohach" <jzb@aexorsyst.com>
To: linux-kernel@vger.kernel.org
Subject: Elf loader question: who updates .rela.dyn entries for load_bias compensation?
Date: Fri, 5 May 2006 09:44:15 -0700 [thread overview]
Message-ID: <200605050944.15440.jzb@aexorsyst.com> (raw)
Apologies if this is the wrong forum, but...
I'm porting Linux to a new architecture, and ran into an issue with
the .rela.dyn entries not being adjusted to compensate for the load_bias
of an ET_DYN shared executable: in particular, this is the ld.so itself that
doesn't get its .rela.dyn entries incremented by +load_bias. This makes
references from _GLOBAL_OFFSET_TABLE_ refer to the old compile-time
vma addresses, which of course causes runtime segfaults (appropriately
enough) with ld.so.
I've poured over binfmt_elf.c to see what it does, but it doesn't appear to
touch any of the sections themselves other than to load them, notably at
p_vaddr + load_bias for .so's.
I tried looking at other architectures to see if I could at least determine what
the proper existing operations are, but came up emtpy. The ET_PLAT_INIT()
macro only updates regisers. This leaves me to assume that the interpreter
itself updates the .rela.dyn entries for shared libs. besides itself, but I can't find
where/how, and how to get it to do so for itself as well.
This only affects ET_DYN type of .so's, because ET_EXEC's don't get a load_bias
and are loaded at the vma for which they were compiled.
Sorry if I sound like a novice...
Thanks for any pointers anyone could provide...
next reply other threads:[~2006-05-05 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 16:44 John Z. Bohach [this message]
2006-05-09 19:02 ` Hagen Paul Pfeifer
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=200605050944.15440.jzb@aexorsyst.com \
--to=jzb@aexorsyst.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®