[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230126152024.bfdd25de2ff5107fa7c02986@linux-foundation.org>
Date: Thu, 26 Jan 2023 15:20:24 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: Andrey Ryabinin <ryabinin.a.a@...il.com>,
Alexander Potapenko <glider@...gle.com>,
Andrey Konovalov <andreyknvl@...il.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Vincenzo Frascino <vincenzo.frascino@....com>,
linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-mm@...ck.org, kasan-dev@...glegroups.com,
Nathan Lynch <nathanl@...ux.ibm.com>,
Michael Ellerman <mpe@...erman.id.au>
Subject: Re: [PATCH] kasan: Fix Oops due to missing calls to
kasan_arch_is_ready()
On Thu, 26 Jan 2023 08:04:47 +0100 Christophe Leroy <christophe.leroy@...roup.eu> wrote:
> On powerpc64, you can build a kernel with KASAN as soon as you build it
> with RADIX MMU support. However if the CPU doesn't have RADIX MMU,
> KASAN isn't enabled at init and the following Oops is encountered.
Should we backport to -stable? If so, can we identify a suitable Fixes: target?
Thanks.
Powered by blists - more mailing lists