From: Andrey Ryabinin <ryabinin.a.a@gmail.com>
To: Baoquan He <bhe@redhat.com>, Andrey Konovalov <andreyknvl@gmail.com>
Cc: linux-mm@kvack.org, glider@google.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 00/12] mm/kasan: make kasan=on|off work for all three modes
Date: Wed, 24 Dec 2025 13:25:50 +0100 [thread overview]
Message-ID: <edd6e350-5482-4551-aa94-e1ab8d2f9774@gmail.com> (raw)
In-Reply-To: <aUtd6es8UC0lNf/9@MiWiFi-R3L-srv>
On 12/24/25 4:28 AM, Baoquan He wrote:
> Hi Andrey,
>
> On 12/04/25 at 05:38pm, Andrey Konovalov wrote:
>> On Fri, Nov 28, 2025 at 4:33 AM Baoquan He <bhe@redhat.com> wrote:
>>>
> ...snip...
>>> Testing:
>>> ========
>>> - Testing on x86_64 and arm64 for generic mode passed when kasan=on or
>>> kasan=off.
>>>
>>> - Testing on arm64 with sw_tags mode passed when kasan=off is set. But
>>> when I tried to test sw_tags on arm64, the system bootup failed. It's
>>> not introduced by my patchset, the original code has the bug. I have
>>> reported it to upstream.
>>> - System is broken in KASAN sw_tags mode during bootup
>>> - https://lore.kernel.org/all/aSXKqJTkZPNskFop@MiWiFi-R3L-srv/T/#u
>>
>> This will hopefully be fixed soon, so you'll be able to test.
>
> Do you have the patch link of the fix on sw_tags breakage?
I think this one should fix it - https://lkml.kernel.org/r/cover.1765978969.git.m.wieczorretman@pm.me
>
> I am organizing patches and testing them for reposting, but still see
> the sw_tags breakage during boot on arm64 system. If you have the
> pointer about the fix, I can grab the possible unmature code change to
> make sw_tags mode work to finish my testing.
>
> Thanks
> Baoquan
>
next prev parent reply other threads:[~2025-12-24 12:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 3:33 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 ` [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
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 [this message]
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=edd6e350-5482-4551-aa94-e1ab8d2f9774@gmail.com \
--to=ryabinin.a.a@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=bhe@redhat.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox