From: Andy Lutomirski <luto@amacapital.net>
To: musl@lists.openwall.com
Subject: vDSO parsing bug?
Date: Thu, 20 Mar 2014 08:23:24 -0700 [thread overview]
Message-ID: <CALCETrU9N8X33Om=k2Q70cSun6RYX94G_aRLKVnYWvHZ_ZfmTQ@mail.gmail.com> (raw)
Hi-
It looks like musl can't handle vDSO images with more than one PT_LOAD
segment. Both glibc and the reference code in
Documentation/vDSO/parse_vdso.c can handle this.
It's not currently an issue, since I don't think that any
architectures provide such a vDSO, but they might want to in the
future.
Also, using the name "linux-gate.so.1" is sort of wrong on x86_64,
where the convention is "linux-vdso.so.1". Wouldn't it be better to
just read the name out of the SONAME header?
--Andy
next reply other threads:[~2014-03-20 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 15:23 Andy Lutomirski [this message]
2014-03-20 17:02 ` Rich Felker
2014-03-20 20:02 ` Andy Lutomirski
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='CALCETrU9N8X33Om=k2Q70cSun6RYX94G_aRLKVnYWvHZ_ZfmTQ@mail.gmail.com' \
--to=luto@amacapital.net \
--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).