about summary refs log tree commit diff
path: root/debug/memset_chk.c
diff options
context:
space:
mode:
authorAdhemerval Zanella <adhemerval.zanella@linaro.org>2024-06-11 12:27:04 -0300
committerAdhemerval Zanella <adhemerval.zanella@linaro.org>2024-06-12 15:25:54 -0300
commit7edd3814b00c46a404cbaf316eab9db18438c3dd (patch)
tree5c5c9eeb8b9f2ab01c182b95ba8fef906499d304 /debug/memset_chk.c
parente7ac92e6ca9784b397189df0b2e1fb34f425bab8 (diff)
downloadglibc-7edd3814b00c46a404cbaf316eab9db18438c3dd.tar.gz
glibc-7edd3814b00c46a404cbaf316eab9db18438c3dd.tar.xz
glibc-7edd3814b00c46a404cbaf316eab9db18438c3dd.zip
linux: Remove __stack_prot
The __stack_prot is used by Linux to make the stack executable if
a modules requires it.  It is also marked as RELRO, which requires
to change the segment permission to RW to update it.

Also, there is no need to keep track of the flags: either the stack
will have the default permission of the ABI or should be change to
PROT_READ | PROT_WRITE | PROT_EXEC.  The only additional flag,
PROT_GROWSDOWN or PROT_GROWSUP, is Linux only and can be deducted
from _STACK_GROWS_DOWN/_STACK_GROWS_UP.

Also, the check_consistency function was already removed some time
ago.

Checked on x86_64-linux-gnu and i686-linux-gnu.
Reviewed-by: Florian Weimer <fweimer@redhat.com>
Diffstat (limited to 'debug/memset_chk.c')
0 files changed, 0 insertions, 0 deletions