From: Hamza Mahfooz <hamza.mahfooz@amd.com>
To: <linux-kernel@vger.kernel.org>
Cc: "Rodrigo Siqueira" <rodrigo.siqueira@amd.com>,
"Harry Wentland" <harry.wentland@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Hamza Mahfooz" <hamza.mahfooz@amd.com>,
stable@vger.kernel.org, "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Nick Terrell" <terrelln@fb.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Tom Rix" <trix@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Kees Cook" <keescook@chromium.org>,
"Zhaoyang Huang" <zhaoyang.huang@unisoc.com>,
"Li Hua" <hucool.lihua@huawei.com>,
"Alexander Potapenko" <glider@google.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Rae Moar" <rmoar@google.com>,
rust-for-linux@vger.kernel.org, bpf@vger.kernel.org,
llvm@lists.linux.dev
Subject: [PATCH] lib/Kconfig.debug: disable FRAME_WARN for kasan and kcsan
Date: Wed, 18 Oct 2023 14:24:11 -0400 [thread overview]
Message-ID: <20231018182412.80291-1-hamza.mahfooz@amd.com> (raw)
With every release of LLVM, both of these sanitizers eat up more and
more of the stack. So, set FRAME_WARN to 0 if either of them is enabled
for a given build.
Cc: stable@vger.kernel.org
Signed-off-by: Hamza Mahfooz <hamza.mahfooz@amd.com>
---
lib/Kconfig.debug | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 39d1d93164bd..15ad742729ca 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -429,11 +429,10 @@ endif # DEBUG_INFO
config FRAME_WARN
int "Warn for stack frames larger than"
range 0 8192
- default 0 if KMSAN
+ default 0 if KASAN || KCSAN || KMSAN
default 2048 if GCC_PLUGIN_LATENT_ENTROPY
default 2048 if PARISC
default 1536 if (!64BIT && XTENSA)
- default 1280 if KASAN && !64BIT
default 1024 if !64BIT
default 2048 if 64BIT
help
--
2.42.0
next reply other threads:[~2023-10-18 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 18:24 Hamza Mahfooz [this message]
2023-10-18 18:29 ` [PATCH] lib/Kconfig.debug: disable FRAME_WARN for kasan and kcsan Geert Uytterhoeven
2023-10-18 18:39 ` Hamza Mahfooz
2023-10-18 19:12 ` Geert Uytterhoeven
2023-10-19 10:04 ` Alexander Potapenko
2023-10-19 12:53 ` Arnd Bergmann
2023-10-19 15:56 ` Nathan Chancellor
2023-10-19 20:17 ` Hamza Mahfooz
2023-10-19 20:51 ` Nathan Chancellor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231018182412.80291-1-hamza.mahfooz@amd.com \
--to=hamza.mahfooz@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alex.gaynor@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=arnd@arndb.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=gary@garyguo.net \
--cc=geert+renesas@glider.be \
--cc=glider@google.com \
--cc=harry.wentland@amd.com \
--cc=hucool.lihua@huawei.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mhiramat@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rmoar@google.com \
--cc=rodrigo.siqueira@amd.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=terrelln@fb.com \
--cc=trix@redhat.com \
--cc=wedsonaf@gmail.com \
--cc=zhaoyang.huang@unisoc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox