[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250721173520.a24c29782de519dab1c59fec@linux-foundation.org>
Date: Mon, 21 Jul 2025 17:35:20 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Andrey Ryabinin <ryabinin.a.a@...il.com>
Cc: Sabyrzhan Tasbolatov <snovitoll@...il.com>, hca@...ux.ibm.com,
christophe.leroy@...roup.eu, andreyknvl@...il.com, agordeev@...ux.ibm.com,
glider@...gle.com, dvyukov@...gle.com, kasan-dev@...glegroups.com,
linux-kernel@...r.kernel.org, loongarch@...ts.linux.dev,
linuxppc-dev@...ts.ozlabs.org, linux-riscv@...ts.infradead.org,
linux-s390@...r.kernel.org, linux-um@...ts.infradead.org,
linux-mm@...ck.org
Subject: Re: [PATCH v3 01/12] lib/kasan: introduce CONFIG_ARCH_DEFER_KASAN
option
On Tue, 22 Jul 2025 01:18:52 +0200 Andrey Ryabinin <ryabinin.a.a@...il.com> wrote:
> >> Architectures that need deferred KASAN should select this option.
> >> Architectures that can enable KASAN early will get compile-time
> >> optimizations instead of runtime checks.
> >
> > Looks nice and appears quite mature. I'm reluctant to add it to mm.git
> > during -rc6, especially given the lack of formal review and ack tags.
> >
> > But but but, that's what the mm-new branch is for. I guess I'll add it
> > to get some additional exposure, but whether I'll advance it into
> > mm-unstable/linux-next for this cycle is unclear.
> >
> > What do you (and others) think?
>
> After looking a bit, it breaks UM and probably LoongArch too.
> I'd say it needs more work and not ready even for mm-new.
OK, thanks. I'll drop the v3 series.
Powered by blists - more mailing lists