[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+fCnZcpLE_uR4D9eyUA9_TzF0w2GgY=yWYB63b2VL1snAQi1Q@mail.gmail.com>
Date: Thu, 23 Nov 2023 04:13:07 +0100
From: Andrey Konovalov <andreyknvl@...il.com>
To: Hyeonggon Yoo <42.hyeyoo@...il.com>
Cc: andrey.konovalov@...ux.dev,
Andrew Morton <akpm@...ux-foundation.org>,
Marco Elver <elver@...gle.com>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Vlastimil Babka <vbabka@...e.cz>, kasan-dev@...glegroups.com,
Evgenii Stepanov <eugenis@...gle.com>,
Oscar Salvador <osalvador@...e.de>,
Feng Tang <feng.tang@...el.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Andrey Konovalov <andreyknvl@...gle.com>
Subject: Re: [PATCH mm] slub, kasan: improve interaction of KASAN and
slub_debug poisoning
On Thu, Nov 23, 2023 at 3:58 AM Hyeonggon Yoo <42.hyeyoo@...il.com> wrote:
>
> 1. I reverted the commit "kasan: improve free meta storage in Generic KASAN",
> on top of linux-next (next-20231122), and it is still stuck at boot.
This is expected: the patch you bisected to still requires this fix
that I posted.
> 2. I reverted the commit "kasan: improve free meta storage in Generic KASAN",
> on top of linux-next (next-20231122),
> _and_ applied this patch on top of it, now it boots fine!
Great! Thank you for testing!
Powered by blists - more mailing lists