glibc/include/bits/sigstack.h

#include_next <bits/sigstack.h>

#if !defined _ISOMAC && !defined CONSTANT_MINSIGSTKSZ
# define CONSTANT_MINSIGSTKSZ MINSIGSTKSZ
#endif
sysconf: Add _SC_MINSIGSTKSZ/_SC_SIGSTKSZ [BZ #20305] Add _SC_MINSIGSTKSZ for the minimum signal stack size derived from AT_MINSIGSTKSZ, which is the minimum number of bytes of free stack space required in order to gurantee successful, non-nested handling of a single signal whose handler is an empty function, and _SC_SIGSTKSZ which is the suggested minimum number of bytes of stack space required for a signal stack. If AT_MINSIGSTKSZ isn't available, sysconf (_SC_MINSIGSTKSZ) returns MINSIGSTKSZ. On Linux/x86 with XSAVE, the signal frame used by kernel is composed of the following areas and laid out as: ------------------------------ \| alignment padding \| ------------------------------ \| xsave buffer \| ------------------------------ \| fsave header (32-bit only) \| ------------------------------ \| siginfo + ucontext \| ------------------------------ Compute AT_MINSIGSTKSZ value as size of xsave buffer + size of fsave header (32-bit only) + size of siginfo and ucontext + alignment padding. If _SC_SIGSTKSZ_SOURCE or _GNU_SOURCE are defined, MINSIGSTKSZ and SIGSTKSZ are redefined as /* Default stack size for a signal handler: sysconf (SC_SIGSTKSZ). / # undef SIGSTKSZ # define SIGSTKSZ sysconf (_SC_SIGSTKSZ) / Minimum stack size for a signal handler: SIGSTKSZ. */ # undef MINSIGSTKSZ # define MINSIGSTKSZ SIGSTKSZ Compilation will fail if the source assumes constant MINSIGSTKSZ or SIGSTKSZ. The reason for not simply increasing the kernel's MINSIGSTKSZ #define (apart from the fact that it is rarely used, due to glibc's shadowing definitions) was that userspace binaries will have baked in the old value of the constant and may be making assumptions about it. For example, the type (char [MINSIGSTKSZ]) changes if this #define changes. This could be a problem if an newly built library tries to memcpy() or dump such an object defined by and old binary. Bounds-checking and the stack sizes passed to things like sigaltstack() and makecontext() could similarly go wrong. 2021-02-01 19:00:38 +00:00			`#include_next <bits/sigstack.h>`

			`#if !defined _ISOMAC && !defined CONSTANT_MINSIGSTKSZ`
			`# define CONSTANT_MINSIGSTKSZ MINSIGSTKSZ`
			`#endif`