glibc/sysdeps/unix/sysv/linux/ia64/localplt.data

libc.so: calloc
libc.so: free
libc.so: malloc
libc.so: memalign
libc.so: realloc
libm.so: matherr
libm.so: matherrf
libm.so: matherrl
# The main malloc is interposed into the dynamic linker, for
# allocations after the initial link (when dlopen is used).
ld.so: malloc
ld.so: calloc
ld.so: realloc
ld.so: free
# The TLS-enabled version of these functions is interposed from libc.so.
ld.so: _dl_signal_error
ld.so: _dl_catch_error
ia64: add matherr[fl] to libm.so plt whitelist The ia64 math code has extra matherr functions (f and l variants), so add them to the libm.so plt whitelist like the existing matherr in the main code. The check-localplt test now passes. Signed-off-by: Mike Frysinger <vapier@gentoo.org> 2012-05-06 22:24:32 +00:00			`libc.so: calloc`
			`libc.so: free`
			`libc.so: malloc`
			`libc.so: memalign`
			`libc.so: realloc`
			`libm.so: matherr`
			`libm.so: matherrf`
			`libm.so: matherrl`
ld.so: Remove __libc_memalign It is no longer needed since commit 6c444ad6e953dbdf9c7be065308a0a777 (elf: Do not use memalign for TCB/TLS blocks allocation [BZ #17730]). Applications do not link against ld.so and will use the definition in libc.so, so there is no ABI impact. 2016-11-30 15:23:58 +00:00			`# The main malloc is interposed into the dynamic linker, for`
			`# allocations after the initial link (when dlopen is used).`
Run check-localpltk/textrel/execstack over ld.so. For maximum paranoia we run ld.so through the normal set of tests for all of the shared libraries. This includes running ld.so through check-localplt, check-textrel, and check-execstack. While none of these should trigger any failures given the way ld.so is built, it might possibly fail if a developer does something wrong. This paranoia was triggered by a discussion over the use of __strcpy vs. strcpy [1] and if the symbol could leak and use the libc.so version. The check-localplt test fails right away because localplt.data needs updating for all arches. By default we add 6 new symbols: __tls_get_addr, __libc_memalign, malloc, calloc, realloc and free. Other machines like i386, power, and s390 require some different symbol sets e.g. ___tls_get_addr vs. __tls_get_addr for i386. Verified for i386 Verified for x86_64 Verified for ppc32 Verified for ppc64 Verified for ppc64le Verified for arm Verified for aarch64 Verified for s390 Verified for s390x Guessed for alpha Guessed for ia64 Guessed for m68k Guessed for microblaze Guessed for sparc32 Guessed for sparc64 Defaults for sh Defaults for mips Defaults for hppa Defaults for tile Machine manintainers notified to double check the data used in localplt.data. [1] https://sourceware.org/ml/libc-alpha/2014-10/msg00548.html 2014-11-06 20:48:44 +00:00			`ld.so: malloc`
			`ld.so: calloc`
			`ld.so: realloc`
			`ld.so: free`
Implement _dl_catch_error, _dl_signal_error in libc.so [BZ #16628] This change moves the main implementation of _dl_catch_error, _dl_signal_error to libc.so, where TLS variables can be used directly. This removes a writable function pointer from the rtld_global variable. For use during initial relocation, minimal implementations of these functions are provided in ld.so. These are eventually interposed by the libc.so implementations. This is implemented by compiling elf/dl-error-skeleton.c twice, via elf/dl-error.c and elf/dl-error-minimal.c. As a side effect of this change, the static version of dl-error.c no longer includes support for the _dl_signal_cerror/_dl_receive_error mechanism because it is only used in ld.so. 2016-11-30 14:59:57 +00:00			`# The TLS-enabled version of these functions is interposed from libc.so.`
			`ld.so: _dl_signal_error`
			`ld.so: _dl_catch_error`