summaryrefslogtreecommitdiff
path: root/lib/Kconfig.kfence
diff options
context:
space:
mode:
authorHeiko Carstens <hca@linux.ibm.com>2024-02-05 18:48:43 +0300
committerHeiko Carstens <hca@linux.ibm.com>2024-02-09 15:58:16 +0300
commitfd7eea27a3aed79b63b1726c00bde0d50cf207e2 (patch)
tree6665675d9021983911d69070e71f28b225beb3d7 /lib/Kconfig.kfence
parent9e99049a80b1a251dc4581ff3031196015b8ad41 (diff)
downloadlinux-fd7eea27a3aed79b63b1726c00bde0d50cf207e2.tar.xz
Compiler Attributes: Add __uninitialized macro
With INIT_STACK_ALL_PATTERN or INIT_STACK_ALL_ZERO enabled the kernel will be compiled with -ftrivial-auto-var-init=<...> which causes initialization of stack variables at function entry time. In order to avoid the performance impact that comes with this users can use the "uninitialized" attribute to prevent such initialization. Therefore provide the __uninitialized macro which can be used for cases where INIT_STACK_ALL_PATTERN or INIT_STACK_ALL_ZERO is enabled, but only selected variables should not be initialized. Acked-by: Kees Cook <keescook@chromium.org> Reviewed-by: Nathan Chancellor <nathan@kernel.org> Link: https://lore.kernel.org/r/20240205154844.3757121-2-hca@linux.ibm.com Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'lib/Kconfig.kfence')
0 files changed, 0 insertions, 0 deletions