[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG_fn=V9FXGpqceojn0UGiPi7gFbDbRnObc-N5a55Qk=XQy=kg@mail.gmail.com>
Date: Fri, 29 Sep 2023 16:05:42 +0200
From: Alexander Potapenko <glider@...gle.com>
To: Joey Jiao <quic_jiangenj@...cinc.com>,
Masahiro Yamada <masahiroy@...nel.org>
Cc: kasan-dev@...glegroups.com, quic_likaid@...cinc.com,
Andrey Ryabinin <ryabinin.a.a@...il.com>,
Andrey Konovalov <andreyknvl@...il.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Vincenzo Frascino <vincenzo.frascino@....com>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Nicolas Schier <nicolas@...sle.eu>,
linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] kasan: Add CONFIG_KASAN_WHITELIST_ONLY mode
(CC Masahiro Yamada)
On Thu, Sep 28, 2023 at 6:16 AM Joey Jiao <quic_jiangenj@...cinc.com> wrote:
>
> Fow low memory device, full enabled kasan just not work.
> Set KASAN_SANITIZE to n when CONFIG_KASAN_WHITELIST_ONLY=y.
> So we can enable kasan for single file or module.
I don't have technical objections here, but it bothers me a bit that
we are adding support for KASAN_SANITIZE:=y, although nobody will be
adding KASAN_SANITIZE:=y to upstream Makefiles - only development
kernels when debugging on low-end devices.
Masahiro, is this something worth having in upstream Kconfig code?
> Signed-off-by: Joey Jiao <quic_jiangenj@...cinc.com>
Reviewed-by: Alexander Potapenko <glider@...gle.com>
Powered by blists - more mailing lists