Kconfig.debug: disable CONFIG_FRAME_WARN for KMSAN by default
authorAlexander Potapenko <glider@google.com>
Mon, 24 Oct 2022 21:21:42 +0000 (23:21 +0200)
committerAndrew Morton <akpm@linux-foundation.org>
Fri, 28 Oct 2022 20:37:23 +0000 (13:37 -0700)
KMSAN adds a lot of instrumentation to the code, which results in
increased stack usage (up to 2048 bytes and more in some cases).  It's
hard to predict how big the stack frames can be, so we disable the
warnings for KMSAN instead.

Link: https://lkml.kernel.org/r/20221024212144.2852069-3-glider@google.com
Link: https://github.com/google/kmsan/issues/89
Signed-off-by: Alexander Potapenko <glider@google.com>
Cc: Kees Cook <keescook@chromium.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
lib/Kconfig.debug

index 3fc7abf..2928007 100644 (file)
@@ -400,8 +400,9 @@ config FRAME_WARN
        default 1536 if (!64BIT && XTENSA)
        default 1024 if !64BIT
        default 2048 if 64BIT
+       default 0 if KMSAN
        help
-         Tell gcc to warn at build time for stack frames larger than this.
+         Tell the compiler to warn at build time for stack frames larger than this.
          Setting this too low will cause a lot of warnings.
          Setting it to 0 disables the warning.