[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <874jsctwcm.fsf@mpe.ellerman.id.au>
Date: Fri, 27 Jan 2023 15:50:01 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Andrew Morton <akpm@...ux-foundation.org>,
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>
Subject: Re: [PATCH] kasan: Fix Oops due to missing calls to
kasan_arch_is_ready()
Andrew Morton <akpm@...ux-foundation.org> writes:
> 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?
It would be nice if it went to stable, but I'd defer to the Kasan maintainers.
The kasan_arch_is_ready() checks went in a while back, but there wasn't
a meaningful user until the powerpc support went in, so I'd target that:
Fixes: 41b7a347bf14 ("powerpc: Book3S 64-bit outline-only KASAN support")
Cc: stable@...r.kernel.org # v5.19+
cheers
Powered by blists - more mailing lists