From: Baoquan He <bhe@redhat.com>
To: Alexander Potapenko <glider@google.com>
Cc: linux-mm@kvack.org, ryabinin.a.a@gmail.com, andreyknvl@gmail.com,
dvyukov@google.com, vincenzo.frascino@arm.com,
akpm@linux-foundation.org, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
elver@google.com, sj@kernel.org, lorenzo.stoakes@oracle.com,
snovitoll@gmail.com, christophe.leroy@csgroup.eu
Subject: Re: [PATCH v4 12/12] mm/kasan: make kasan=on|off take effect for all three modes
Date: Sun, 30 Nov 2025 10:49:18 +0800 [thread overview]
Message-ID: <aSuwrkCSxvffKAZc@MiWiFi-R3L-srv> (raw)
In-Reply-To: <CAG_fn=WpLtVhhOfU3pBKbJ2P3ih+PX4oW+MKAAmHRW0onOgSvg@mail.gmail.com>
On 11/28/25 at 04:50pm, Alexander Potapenko wrote:
> > @@ -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.
You are right, that line should be removed. Thanks for careful checking.
> > static __always_inline bool kasan_enabled(void)
> > {
> > - return IS_ENABLED(CONFIG_KASAN);
> > + return false;
> > }
>
next prev parent reply other threads:[~2025-11-30 2:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 3:33 [PATCH v4 00/12] mm/kasan: make kasan=on|off work for all three modes Baoquan He
2025-11-28 3:33 ` [PATCH v4 01/12] mm/kasan: add conditional checks in functions to return directly if kasan is disabled Baoquan He
2025-12-04 16:38 ` Andrey Konovalov
2025-12-05 7:20 ` Baoquan He
2025-12-05 15:07 ` Andrey Konovalov
2025-11-28 3:33 ` [PATCH v4 02/12] mm/kasan: move kasan= code to common place Baoquan He
2025-12-04 16:39 ` Andrey Konovalov
2025-12-09 3:27 ` Baoquan He
2025-11-28 3:33 ` [PATCH v4 03/12] mm/kasan/sw_tags: don't initialize kasan if it's disabled Baoquan He
2025-12-04 16:40 ` Andrey Konovalov
2025-11-28 3:33 ` [PATCH v4 04/12] arch/arm: " Baoquan He
2025-11-28 3:33 ` [PATCH v4 05/12] arch/arm64: " Baoquan He
2025-11-28 3:33 ` [PATCH v4 06/12] arch/loongarch: " Baoquan He
2025-11-28 3:33 ` [PATCH v4 07/12] arch/powerpc: " Baoquan He
2025-11-28 3:33 ` [PATCH v4 08/12] arch/riscv: " Baoquan He
2025-11-28 3:33 ` Baoquan He
2025-11-28 3:33 ` [PATCH v4 09/12] arch/x86: " Baoquan He
2025-11-28 3:33 ` [PATCH v4 10/12] arch/xtensa: " Baoquan He
2025-11-28 3:33 ` [PATCH v4 11/12] arch/um: " Baoquan He
2025-12-01 10:56 ` Johannes Berg
2025-12-02 13:13 ` Baoquan He
2025-11-28 3:33 ` [PATCH v4 12/12] mm/kasan: make kasan=on|off take effect for all three modes Baoquan He
2025-11-28 15:50 ` Alexander Potapenko
2025-11-30 2:49 ` Baoquan He [this message]
2025-12-04 16:40 ` Andrey Konovalov
2025-12-04 16:38 ` [PATCH v4 00/12] mm/kasan: make kasan=on|off work " Andrey Konovalov
2025-12-05 7:14 ` Baoquan He
2025-12-05 11:03 ` Heiko Carstens
2025-12-05 12:57 ` Baoquan He
2025-12-05 15:07 ` Andrey Konovalov
2025-12-24 3:28 ` Baoquan He
2025-12-24 12:25 ` Andrey Ryabinin
2025-12-25 2:26 ` Baoquan He
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=aSuwrkCSxvffKAZc@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=ryabinin.a.a@gmail.com \
--cc=sj@kernel.org \
--cc=snovitoll@gmail.com \
--cc=vincenzo.frascino@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.