[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG_fn=WpLtVhhOfU3pBKbJ2P3ih+PX4oW+MKAAmHRW0onOgSvg@mail.gmail.com>
Date: Fri, 28 Nov 2025 16:50:51 +0100
From: Alexander Potapenko <glider@...gle.com>
To: Baoquan He <bhe@...hat.com>
Cc: linux-mm@...ck.org, ryabinin.a.a@...il.com, andreyknvl@...il.com,
dvyukov@...gle.com, vincenzo.frascino@....com, akpm@...ux-foundation.org,
kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org,
kexec@...ts.infradead.org, elver@...gle.com, sj@...nel.org,
lorenzo.stoakes@...cle.com, snovitoll@...il.com, christophe.leroy@...roup.eu
Subject: Re: [PATCH v4 12/12] mm/kasan: make kasan=on|off take effect for all
three modes
> @@ -30,7 +30,7 @@ static inline void kasan_enable(void)
> /* For architectures that can enable KASAN early, use compile-time check. */
I think the behavior of kasan_enabled() is inconsistent with this comment now.
> static __always_inline bool kasan_enabled(void)
> {
> - return IS_ENABLED(CONFIG_KASAN);
> + return false;
> }
Powered by blists - more mailing lists