diff options
author | Szabolcs Nagy <szabolcs.nagy@arm.com> | 2021-01-19 17:17:01 +0000 |
---|---|---|
committer | Szabolcs Nagy <szabolcs.nagy@arm.com> | 2021-01-21 15:55:10 +0000 |
commit | 86d439b06fb29af8d063ee8855ff63a863f46ef3 (patch) | |
tree | e276fafa0911c561e05afab86df2127909299945 /include/libc-symbols.h | |
parent | 47618209d05a0e77932038f21c6bba2425bd75c6 (diff) | |
download | glibc-86d439b06fb29af8d063ee8855ff63a863f46ef3.tar.gz glibc-86d439b06fb29af8d063ee8855ff63a863f46ef3.tar.xz glibc-86d439b06fb29af8d063ee8855ff63a863f46ef3.zip |
csu: Move static pie self relocation later [BZ #27072]
IFUNC resolvers may depend on tunables and cpu feature setup so move static pie self relocation after those. It is hard to guarantee that the ealy startup code does not rely on relocations so this is a bit fragile. It would be more robust to handle RELATIVE relocs early and only IRELATIVE relocs later, but the current relocation processing code cannot do that. The early startup code up to relocation processing includes _dl_aux_init (auxvec); __libc_init_secure (); __tunables_init (__environ); ARCH_INIT_CPU_FEATURES (); _dl_relocate_static_pie (); These are simple enough that RELATIVE relocs can be avoided. The following steps include ARCH_SETUP_IREL (); ARCH_SETUP_TLS (); ARCH_APPLY_IREL (); On some targets IRELATIVE processing relies on TLS setup on others TLS setup relies on IRELATIVE relocs, so the right position for _dl_relocate_static_pie is target dependent. For now move self relocation as early as possible on targets that support static PIE. Fixes bug 27072. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Diffstat (limited to 'include/libc-symbols.h')
0 files changed, 0 insertions, 0 deletions