From: Baoquan He <bhe@redhat.com>
To: linux-mm@kvack.org
Cc: snovitoll@gmail.com, ryabinin.a.a@gmail.com,
christophe.leroy@csgroup.eu, hca@linux.ibm.com,
andreyknvl@gmail.com, akpm@linux-foundation.org,
chenhuacai@loongson.cn, davidgow@google.com, glider@google.com,
dvyukov@google.com, alexghiti@rivosinc.com,
kasan-dev@googlegroups.com, loongarch@lists.linux.dev,
linuxppc-dev@lists.ozlabs.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org, agordeev@linux.ibm.com,
Baoquan He <bhe@redhat.com>
Subject: [PATCH 0/4] mm/kasan: remove kasan_arch_is_ready()
Date: Tue, 12 Aug 2025 21:09:29 +0800 [thread overview]
Message-ID: <20250812130933.71593-1-bhe@redhat.com> (raw)
These are made on top of below patchset in which all functional functions
will be skipped if kasan is disabled by checking kasan_enabled(). With
the changes, kasan_arch_is_ready() can be easily cleaned up to simplify
code.
[PATCH v2 00/12] mm/kasan: make kasan=on|off work for all three modes
https://lore.kernel.org/all/20250812124941.69508-1-bhe@redhat.com/T/#u
The 1st three patches are from Sabyrzhan Tasbolatov's patchset. After
clean up the kasan_arch_is_ready() definition in loongarch, power and UM,
we can simply remove kasan_arch_is_ready() checking in mm/kasan since
all the checking has been covered by kasan_enabled().
[PATCH v6 0/2] kasan: unify kasan_enabled() and remove arch-specific implementations
https://lore.kernel.org/all/20250810125746.1105476-1-snovitoll@gmail.com/T/#u
Test:
======
I have tested the effect of this patchset on loongarch, power and UM.
Will try to find machine to do testing.
Baoquan He (1):
mm/kasan: remove kasan_arch_is_ready()
Sabyrzhan Tasbolatov (3):
arch/loongarch: remove kasan_arch_is_ready()
arch/powerpc: remove kasan_arch_is_ready()
arch/um: remove kasan_arch_is_ready()
arch/loongarch/include/asm/kasan.h | 7 -------
arch/loongarch/mm/kasan_init.c | 10 +++-------
arch/powerpc/include/asm/kasan.h | 13 -------------
arch/powerpc/mm/kasan/init_book3s_64.c | 4 ----
arch/um/include/asm/kasan.h | 5 ++---
arch/um/kernel/mem.c | 6 +++++-
mm/kasan/common.c | 9 +++------
mm/kasan/generic.c | 9 ---------
mm/kasan/kasan.h | 6 ------
mm/kasan/shadow.c | 18 ------------------
10 files changed, 13 insertions(+), 74 deletions(-)
--
2.41.0
next reply other threads:[~2025-08-12 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 13:09 Baoquan He [this message]
2025-08-12 13:09 ` [PATCH 1/4] arch/loongarch: " Baoquan He
2025-08-12 13:09 ` [PATCH 2/4] arch/powerpc: " Baoquan He
2025-08-12 13:09 ` [PATCH 3/4] arch/um: " Baoquan He
2025-08-12 13:09 ` [PATCH 4/4] mm/kasan: " 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=20250812130933.71593-1-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=andreyknvl@gmail.com \
--cc=chenhuacai@loongson.cn \
--cc=christophe.leroy@csgroup.eu \
--cc=davidgow@google.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hca@linux.ibm.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-um@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=ryabinin.a.a@gmail.com \
--cc=snovitoll@gmail.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
all inboxes | Powered by JetHome®