From: Fangrui Song <maskray@google.com>
To: libc-alpha@sourceware.org,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>
Subject: [PATCH 0/3] Simplify ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA and revert aarch64/arm's extern protected data handling
Date: Sat, 30 Apr 2022 23:06:12 -0700 [thread overview]
Message-ID: <20220501060615.1694317-1-maskray@google.com> (raw)
Say both a.so and b.so define protected var and the executable copy
relocates var. ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA has strange
semantics: a.so accesses the copy in the executable while b.so accesses
its own. This behavior requires that (a) the compiler emits
GOT-generating relocations (b) the linker produces GLOB_DAT instead of
RELATIVE.
Without the ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA code, b.so's GLOB_DAT
will bind to the executable (normal behavior).
For aarch64/arm it makes sense to restore the original behavior and don't
pay the ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA cost. The behavior is very
unlikely used by anyone.
* Clang code generation treats STV_PROTECTED the same way as STV_HIDDEN:
no GOT-generating relocation in the first place.
* gold and lld reject copy relocation on a STV_PROTECTED symbol.
* Nowadays -fpie/-fpic modes are popular. GCC/Clang's codegen uses
GOT-generating relocation when accessing an default visibility
external symbol which avoids copy relocation.
Fangrui Song (3):
elf: Remove ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA check for
non-DL_EXTERN_PROTECTED_DATA ports
Revert "[AArch64][BZ #17711] Fix extern protected data handling"
Revert "[ARM][BZ #17711] Fix extern protected data handling"
elf/dl-lookup.c | 46 ++++++++++++------------------------
sysdeps/aarch64/dl-machine.h | 13 +++++-----
sysdeps/aarch64/dl-sysdep.h | 2 --
sysdeps/arm/dl-machine.h | 10 +++-----
sysdeps/arm/dl-sysdep.h | 2 --
5 files changed, 24 insertions(+), 49 deletions(-)
--
2.36.0.464.gb9c8b46e94-goog
next reply other threads:[~2022-05-01 6:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 6:06 Fangrui Song [this message]
2022-05-01 6:06 ` [PATCH 1/3] elf: Remove ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA check for non-DL_EXTERN_PROTECTED_DATA ports Fangrui Song
2022-05-01 6:06 ` [PATCH 2/3] Revert "[AArch64][BZ #17711] Fix extern protected data handling" Fangrui Song
2022-05-23 20:10 ` Szabolcs Nagy
2022-05-23 20:17 ` Fangrui Song
2022-05-24 5:13 ` Fangrui Song
2022-05-01 6:06 ` [PATCH 3/3] Revert "[ARM][BZ " Fangrui Song
2022-05-23 20:11 ` Szabolcs Nagy
2022-05-23 20:45 ` Fangrui Song
2022-05-09 21:26 ` [PATCH 0/3] Simplify ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA and revert aarch64/arm's extern protected data handling H.J. Lu
2022-05-10 7:42 ` Fangrui Song
2022-05-10 15:02 ` H.J. Lu
2022-05-12 4:56 ` Fangrui Song
2022-05-13 22:18 ` H.J. Lu
2022-05-13 23:09 ` Fangrui Song
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=20220501060615.1694317-1-maskray@google.com \
--to=maskray@google.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@arm.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.
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).