diff options
author | Fangrui Song <i@maskray.me> | 2022-06-22 10:55:12 -0700 |
---|---|---|
committer | Fangrui Song <i@maskray.me> | 2022-06-22 10:55:12 -0700 |
commit | 90b7a5df152a64d2bea20beb438e8b81049a5c30 (patch) | |
tree | 02a86981b9fab3de79108a80950f35c1a2825353 /gdb/interps.h | |
parent | f18acc9c4e5d18f4783f3a7d59e3ec95d7af0199 (diff) | |
download | gdb-90b7a5df152a64d2bea20beb438e8b81049a5c30.zip gdb-90b7a5df152a64d2bea20beb438e8b81049a5c30.tar.gz gdb-90b7a5df152a64d2bea20beb438e8b81049a5c30.tar.bz2 |
aarch64: Disallow copy relocations on protected data
If an executable has copy relocations for extern protected data, that
can only work if the shared object containing the definition is built
with assumptions (a) the compiler emits GOT-generating relocations (b)
the linker produces R_*_GLOB_DAT instead of R_*_RELATIVE. Otherwise the
shared object uses its own definition directly and the executable
accesses a stale copy. Note: the GOT relocations defeat the purpose of
protected visibility as an optimization, and it turns out this never
worked perfectly.
glibc 2.36 will warn on copy relocations on protected data. Let's
produce a warning at link time, matching ld.lld which has been used on
many aarch64 OSes.
Note: x86 requires GNU_PROPERTY_NO_COPY_ON_PROTECTED to have the error.
This is to largely due to GCC 5's "x86-64: Optimize access to globals in
PIE with copy reloc" which started to use direct access relocations for
external data symbols in -fpie mode.
GCC's aarch64 port does not have the change. Nowadays with most builds
switching to -fpie/-fpic, aarch64 mostly doesn't need to worry about
copy relocations. So for aarch64 we simply don't check
GNU_PROPERTY_NO_COPY_ON_PROTECTED.
Diffstat (limited to 'gdb/interps.h')
0 files changed, 0 insertions, 0 deletions