[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d764242f-cde0-47c0-ae2c-f94b199c93df@amd.com>
Date: Wed, 18 Oct 2023 14:39:48 -0400
From: Hamza Mahfooz <hamza.mahfooz@....com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: linux-kernel@...r.kernel.org,
Rodrigo Siqueira <rodrigo.siqueira@....com>,
Harry Wentland <harry.wentland@....com>,
Alex Deucher <alexander.deucher@....com>,
Arnd Bergmann <arnd@...db.de>, stable@...r.kernel.org,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Nick Terrell <terrelln@...com>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Tom Rix <trix@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Masami Hiramatsu (Google)" <mhiramat@...nel.org>,
Randy Dunlap <rdunlap@...radead.org>,
Kees Cook <keescook@...omium.org>,
Zhaoyang Huang <zhaoyang.huang@...soc.com>,
Li Hua <hucool.lihua@...wei.com>,
Alexander Potapenko <glider@...gle.com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Rae Moar <rmoar@...gle.com>, rust-for-linux@...r.kernel.org,
bpf@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH] lib/Kconfig.debug: disable FRAME_WARN for kasan and kcsan
On 10/18/23 14:29, Geert Uytterhoeven wrote:
> Hi Hamza,
>
> On Wed, Oct 18, 2023 at 8:24 PM Hamza Mahfooz <hamza.mahfooz@....com> wrote:
>> 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@...r.kernel.org
>> Signed-off-by: Hamza Mahfooz <hamza.mahfooz@....com>
>
> Thanks for your patch!
>
>> --- 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
>
> Are kernels with KASAN || KCSAN || KMSAN enabled supposed to be bootable?
They are all intended to be used for runtime debugging, so I'd imagine so.
> Stack overflows do cause crashes.
It is worth noting that FRAME_WARN has been disabled for KMSAN for quite
a while and as far as I can tell no one has complained.
>
>> 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
>
> Gr{oetje,eeting}s,
>
> Geert
>
--
Hamza
Powered by blists - more mailing lists