From: Andrey Konovalov <andreyknvl@gmail.com>
To: Hyeonggon Yoo <42.hyeyoo@gmail.com>
Cc: andrey.konovalov@linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Marco Elver <elver@google.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
kasan-dev@googlegroups.com,
Evgenii Stepanov <eugenis@google.com>,
Oscar Salvador <osalvador@suse.de>,
Feng Tang <feng.tang@intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrey Konovalov <andreyknvl@google.com>
Subject: Re: [PATCH mm] slub, kasan: improve interaction of KASAN and slub_debug poisoning
Date: Thu, 23 Nov 2023 04:13:07 +0100 [thread overview]
Message-ID: <CA+fCnZcpLE_uR4D9eyUA9_TzF0w2GgY=yWYB63b2VL1snAQi1Q@mail.gmail.com> (raw)
In-Reply-To: <CAB=+i9RnOz0jDockOfw3oNageCUF5gmF+nzOzPpoTxtr7eqn7g@mail.gmail.com>
On Thu, Nov 23, 2023 at 3:58 AM Hyeonggon Yoo <42.hyeyoo@gmail.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!
next prev parent reply other threads:[~2023-11-23 3:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 23:12 andrey.konovalov
2023-11-23 0:39 ` Hyeonggon Yoo
2023-11-23 2:30 ` Andrey Konovalov
2023-11-23 2:58 ` Hyeonggon Yoo
2023-11-23 3:13 ` Andrey Konovalov [this message]
2023-11-23 6:26 ` Feng Tang
2023-11-23 12:39 ` Feng Tang
2023-11-23 16:12 ` Andrey Konovalov
2023-11-24 0:45 ` Feng Tang
2023-11-27 11:44 ` Vlastimil Babka
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='CA+fCnZcpLE_uR4D9eyUA9_TzF0w2GgY=yWYB63b2VL1snAQi1Q@mail.gmail.com' \
--to=andreyknvl@gmail.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrey.konovalov@linux.dev \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=feng.tang@intel.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=vbabka@suse.cz \
/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