From: "Maciej W. Rozycki" <macro@mips.com>
To: <libc-alpha@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Alan Modra <amodra@gmail.com>,
"Cary Coutant" <ccoutant@gmail.com>
Subject: [PATCH v2 0/2] Correct absolute (SHN_ABS) symbol run-time calculation [BZ #19818]
Date: Tue, 20 Feb 2018 18:40:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1802201804140.3553@tp.orcam.me.uk> (raw)
Hi,
This mini patch series addresses the issue filed as BZ #19818 where
absolute (SHN_ABS) symbol are incorrectly relocated by the base address at
run time, whereas their values are supposed to remain unaffected by
relocation.
As we have run-time symbol address calculations (often made in a slightly
but insignificantly different way) scattered throughout our tree I have
decided to unify all that code, hopefully making it cleaner and easier to
maintain, and made it patch 1/2 in this series. Then patch 2/2 is the
actual fix, which owing to 1/2 has become a one-liner.
This updated v2 addresses Andreas's concern and an issue with dladdr(3)
family of calls. It has been regression-tested with the `i686-linux' and
`x86_64-linux' targets.
See individual change descriptions for details.
Maciej
next reply other threads:[~2018-02-20 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 18:40 Maciej W. Rozycki [this message]
2018-02-20 18:52 ` [PATCH v2 1/2] elf: Unify symbol address " Maciej W. Rozycki
2018-03-07 20:23 ` Adhemerval Zanella
2018-04-04 22:18 ` Maciej W. Rozycki
2018-02-20 20:24 ` [PATCH v2 2/2] elf: Correct absolute (SHN_ABS) symbol " Maciej W. Rozycki
2018-03-07 20:25 ` Adhemerval Zanella
2018-03-08 15:40 ` Florian Weimer
2018-04-04 22:20 ` Maciej W. Rozycki
2018-03-01 15:15 ` [PING][PATCH v2 0/2] " Maciej W. Rozycki
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=alpine.DEB.2.00.1802201804140.3553@tp.orcam.me.uk \
--to=macro@mips.com \
--cc=amodra@gmail.com \
--cc=ccoutant@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).