Exclude routines from fortification
authorFrédéric Bérat <fberat@redhat.com>
Fri, 17 Mar 2023 09:17:28 +0000 (10:17 +0100)
committerFrédéric Bérat <fberat@redhat.com>
Wed, 5 Jul 2023 14:59:48 +0000 (16:59 +0200)
commit20c894d21eb64153abf7c7f96e6a151897cf1488
tree41038a7e2daf61f19d10f4804313e8e33430046b
parent64d9580cdf7e417170abbef0327e04b29712e949
Exclude routines from fortification

Since the _FORTIFY_SOURCE feature uses some routines of Glibc, they need to
be excluded from the fortification.

On top of that:
 - some tests explicitly verify that some level of fortification works
   appropriately, we therefore shouldn't modify the level set for them.
 - some objects need to be build with optimization disabled, which
   prevents _FORTIFY_SOURCE to be used for them.

Assembler files that implement architecture specific versions of the
fortified routines were not excluded from _FORTIFY_SOURCE as there is no
C header included that would impact their behavior.

Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
17 files changed:
debug/Makefile
io/Makefile
libio/Makefile
login/Makefile
misc/Makefile
posix/Makefile
rt/Makefile
setjmp/Makefile
socket/Makefile
stdio-common/Makefile
stdlib/Makefile
string/Makefile
sysdeps/ieee754/ldbl-128ibm-compat/Makefile
sysdeps/ieee754/ldbl-opt/Makefile
sysdeps/pthread/Makefile
sysdeps/unix/sysv/linux/Makefile
wcsmbs/Makefile