From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Cc: Andreas Schwab <schwab@suse.de>, Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH v2 2/2] elf: Correct absolute (SHN_ABS) symbol run-time calculation [BZ #19818]
Date: Wed, 07 Mar 2018 20:25:00 -0000 [thread overview]
Message-ID: <c5dfeee0-25c0-ef60-a977-dd8f812a4a4b@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1802201815060.3553@tp.orcam.me.uk>
On 20/02/2018 15:38, Maciej W. Rozycki wrote:
> Do not relocate absolute symbols by the base address. Such symbols have
> SHN_ABS as the section index and their value is not supposed to be
> affected by relocation as per the ELF gABI[1]:
>
> "SHN_ABS
> The symbol has an absolute value that will not change because of
> relocation."
>
> The reason for our non-conformance here seems to be an old SysV linker
> bug causing symbols like _DYNAMIC to be incorrectly emitted as absolute
> symbols[2]. However in a previous discussion it was pointed that this
> is seriously flawed by preventing the lone purpose of the existence of
> absolute symbols from being used[3]:
>
> "On the contrary, the only interpretation that makes sense to me is that
> it will not change because of relocation at link time or at load time.
> Absolute symbols, from the days of the earliest linking loaders, have
> been used to represent addresses that are outside the address space of
> the module (e.g., memory-mapped addresses or kernel gateway pages).
> They've even been used to represent true symbolic constants (e.g.,
> system entry point numbers, sizes, version numbers). There's no other
> way to represent a true absolute symbol, while the meaning you seek is
> easily represented by giving the symbol a non-negative st_shndx value."
>
> and we ought to stop supporting our current broken interpretation.
>
> Update processing for dladdr(3) and dladdr1(3) so that SHN_ABS symbols
> are ignored, because under the corrected interpretation they do not
> represent addresses within a mapped file and therefore are not supposed
> to be considered.
>
> References:
>
> [1] "System V Application Binary Interface - DRAFT - 19 October 2010",
> The SCO Group, Section "Symbol Table",
> <http://www.sco.com/developers/gabi/2012-12-31/ch4.symtab.html>
>
> [2] Alan Modra, "Absolute symbols"
> <https://sourceware.org/ml/binutils/2012-05/msg00019.html>
>
> [3] Cary Coutant, "Re: Absolute symbols"
> <https://sourceware.org/ml/binutils/2012-05/msg00020.html>
>
> [BZ #19818]
> * sysdeps/generic/ldsodefs.h (SYMBOL_ADDRESS): Handle SHN_ABS
> symbols.
> * elf/dl-addr.c (determine_info): Ignore SHN_ABS symbols.
> * elf/tst-absolute-sym.c: New file.
> * elf/tst-absolute-sym-lib.c: New file.
> * elf/tst-absolute-sym-lib.lds: New file.
> * elf/Makefile (tests): Add `tst-absolute-sym'.
> (modules-names): Add `tst-absolute-sym-lib'.
> (LDLIBS-tst-absolute-sym-lib.so): New variable.
> ($(objpfx)tst-absolute-sym-lib.so): New dependency.
> ($(objpfx)tst-absolute-sym): New dependency.
The patch and rationale looks reasonable, Andrea and Florian do you still have
objections or doubts about the patch?
next prev parent reply other threads:[~2018-03-07 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 18:40 [PATCH v2 0/2] " Maciej W. Rozycki
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 [this message]
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=c5dfeee0-25c0-ef60-a977-dd8f812a4a4b@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).