Revision b02faed15d86f846b0f23f47b92e0782baa873ed authored by Mark Rutland on 03 October 2017, 17:25:46 UTC, committed by Catalin Marinas on 04 October 2017, 16:37:33 UTC
AddressSanitizer instrumentation can significantly bloat the stack, and
with GCC 7 this can result in stack overflows at boot time in some
configurations.

We can avoid this by doubling our stack size when KASAN is in use, as is
already done on x86 (and has been since KASAN was introduced).
Regardless of other patches to decrease KASAN's stack utilization,
kernels built with KASAN will always require more stack space than those
built without, and we should take this into account.

Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Will Deacon <will.deacon@arm.com>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
1 parent 37f6b42
History
File Mode Size
apparmor
integrity
keys
loadpin
selinux
smack
tomoyo
yama
Kconfig -rw-r--r-- 8.9 KB
Makefile -rw-r--r-- 989 bytes
commoncap.c -rw-r--r-- 36.8 KB
device_cgroup.c -rw-r--r-- 21.0 KB
inode.c -rw-r--r-- 10.5 KB
lsm_audit.c -rw-r--r-- 10.7 KB
min_addr.c -rw-r--r-- 1.3 KB
security.c -rw-r--r-- 42.7 KB

back to top