From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Dynamic linker refactoring
Date: Fri, 20 Jan 2012 20:05:54 -0500 [thread overview]
Message-ID: <20120121010554.GA8306@brightrain.aerifal.cx> (raw)
Hi all,
After the recent dynamic linker fixes, I've looked into refactoring
(mainly eliminating logic duplication) and cleaning up the dynamic
linker. As a heads-up, I'm leaning towards stripping out the vdso
(linux-gate) support at the dynamic linker level entirely, and instead
using Nik's original design for vdso-assisted clock_gettime which can
work with static linking too. This cuts out some complexity and code
duplication in the dynamic linker (at the expense of duplicating the
same code elsewhere for use outside the dynamic linker), but the real
benefit is that we don't have to worry about the kernel devs doing
something stupid and polluting the userspace symbol namespace (and
potentially redirecting functions to do the wrong thing) if they add
stuff to the vdso that doesn't belong there. If anyone's against these
changes or wants to discuss them more, please reply in this thread in
the next day or so..
Rich
next reply other threads:[~2012-01-21 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 1:05 Rich Felker [this message]
2012-01-21 12:19 ` aep
2012-01-22 4:30 ` Rich Felker
2012-01-22 12:45 ` aep
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=20120121010554.GA8306@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).