Commit 921757bc authored by Alexander Potapenko's avatar Alexander Potapenko Committed by Andrew Morton

Kconfig.debug: disable CONFIG_FRAME_WARN for KMSAN by default

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/89Signed-off-by: default avatarAlexander 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: default avatarAndrew Morton <akpm@linux-foundation.org>
parent 42855f58
...@@ -400,8 +400,9 @@ config FRAME_WARN ...@@ -400,8 +400,9 @@ config FRAME_WARN
default 1536 if (!64BIT && XTENSA) default 1536 if (!64BIT && XTENSA)
default 1024 if !64BIT default 1024 if !64BIT
default 2048 if 64BIT default 2048 if 64BIT
default 0 if KMSAN
help 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 this too low will cause a lot of warnings.
Setting it to 0 disables the warning. Setting it to 0 disables the warning.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment