From: patchwork-bot+linux-riscv@kernel•org
To: Sabyrzhan Tasbolatov <snovitoll@gmail•com>
Cc: linux-riscv@lists•infradead.org, ryabinin.a.a@gmail•com,
christophe.leroy@csgroup•eu, bhe@redhat•com, hca@linux•ibm.com,
andreyknvl@gmail•com, akpm@linux-foundation•org,
zhangqing@loongson•cn, chenhuacai@loongson•cn,
davidgow@google•com, glider@google•com, dvyukov@google•com,
alexghiti@rivosinc•com, alex@ghiti•fr, agordeev@linux•ibm.com,
vincenzo.frascino@arm•com, elver@google•com,
kasan-dev@googlegroups•com, linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org, loongarch@lists•linux.dev,
linuxppc-dev@lists•ozlabs.org, linux-s390@vger•kernel.org,
linux-um@lists•infradead.org, linux-mm@kvack•org
Subject: Re: [PATCH v6 0/2] kasan: unify kasan_enabled() and remove arch-specific implementations
Date: Thu, 09 Oct 2025 01:07:06 +0000 [thread overview]
Message-ID: <175997202628.3661959.104646439887808862.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250810125746.1105476-1-snovitoll@gmail.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Andrew Morton <akpm@linux-foundation•org>:
On Sun, 10 Aug 2025 17:57:44 +0500 you wrote:
> This patch series addresses the fragmentation in KASAN initialization
> across architectures by introducing a unified approach that eliminates
> duplicate static keys and arch-specific kasan_arch_is_ready()
> implementations.
>
> The core issue is that different architectures have inconsistent approaches
> to KASAN readiness tracking:
> - PowerPC, LoongArch, and UML arch, each implement own kasan_arch_is_ready()
> - Only HW_TAGS mode had a unified static key (kasan_flag_enabled)
> - Generic and SW_TAGS modes relied on arch-specific solutions
> or always-on behavior
>
> [...]
Here is the summary with links:
- [v6,1/2] kasan: introduce ARCH_DEFER_KASAN and unify static key across modes
https://git.kernel.org/riscv/c/1e338f4d99e6
- [v6,2/2] kasan: call kasan_init_generic in kasan_init
https://git.kernel.org/riscv/c/e45085f2673b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-10-09 1:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 12:57 [PATCH v6 0/2] kasan: unify kasan_enabled() and remove arch-specific implementations Sabyrzhan Tasbolatov
2025-08-10 12:57 ` [PATCH v6 1/2] kasan: introduce ARCH_DEFER_KASAN and unify static key across modes Sabyrzhan Tasbolatov
2025-08-11 5:38 ` Christophe Leroy
2025-09-03 13:00 ` Andrey Konovalov
2025-09-03 13:01 ` Andrey Konovalov
2025-09-15 4:30 ` Sabyrzhan Tasbolatov
2025-09-16 3:36 ` Andrew Morton
2025-09-23 17:49 ` Andrey Konovalov
2025-09-04 0:24 ` Ritesh Harjani
2025-10-09 15:59 ` Sabyrzhan Tasbolatov
2025-08-10 12:57 ` [PATCH v6 2/2] kasan: call kasan_init_generic in kasan_init Sabyrzhan Tasbolatov
2025-08-11 5:39 ` Christophe Leroy
2025-10-09 1:07 ` patchwork-bot+linux-riscv [this message]
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=175997202628.3661959.104646439887808862.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel$(echo .)org \
--cc=agordeev@linux$(echo .)ibm.com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=alex@ghiti$(echo .)fr \
--cc=alexghiti@rivosinc$(echo .)com \
--cc=andreyknvl@gmail$(echo .)com \
--cc=bhe@redhat$(echo .)com \
--cc=chenhuacai@loongson$(echo .)cn \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=davidgow@google$(echo .)com \
--cc=dvyukov@google$(echo .)com \
--cc=elver@google$(echo .)com \
--cc=glider@google$(echo .)com \
--cc=hca@linux$(echo .)ibm.com \
--cc=kasan-dev@googlegroups$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux-um@lists$(echo .)infradead.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=loongarch@lists$(echo .)linux.dev \
--cc=ryabinin.a.a@gmail$(echo .)com \
--cc=snovitoll@gmail$(echo .)com \
--cc=vincenzo.frascino@arm$(echo .)com \
--cc=zhangqing@loongson$(echo .)cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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