From: Andrey Konovalov <andreyknvl@gmail.com>
To: Alexander Potapenko <glider@google.com>, Will Deacon <will@kernel.org>
Cc: catalin.marinas@arm.com, ryabinin.a.a@gmail.com, pcc@google.com,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: HW-KASAN and CONFIG_SLUB_DEBUG_ON=y screams about redzone corruption
Date: Tue, 4 Jul 2023 17:29:50 +0200 [thread overview]
Message-ID: <CA+fCnZfkmmdP1ewgVZBLKu9ctZfE61RU=q6oyxHAy5O_Uegs=w@mail.gmail.com> (raw)
In-Reply-To: <CAG_fn=UW0pX5+kRqqr9LH5wYbvA=1rABW8K+trGd-Jt8aynTww@mail.gmail.com>
On Tue, Jul 4, 2023 at 9:42 AM Alexander Potapenko <glider@google.com> wrote:
>
> > While debugging something else, I ended up running v6.4 on an arm64 (v9)
> > fastmodel with both CONFIG_SLUB_DEBUG_ON=y and CONFIG_KASAN_HW_TAGS=y.
> > This makes the system pretty unusable, as I see a tonne of kmalloc
> > Redzone corruption messages pretty much straight out of startup (example
> > below).
I've reproduced the issue, looking into the root cause.
> Does the problem reproduce with CONFIG_KASAN_SW_TAGS?
Looks like SW_TAGS is not affected.
> Also, any chance you could share the file:line info for the stack trace below?
>
> I myself haven't expected KASAN to work together with SLUB_DEBUG...
This was implemented at some point, so it should work.
Thanks!
prev parent reply other threads:[~2023-07-04 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 15:47 Will Deacon
2023-07-04 7:41 ` Alexander Potapenko
2023-07-04 15:29 ` Andrey Konovalov [this message]
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+fCnZfkmmdP1ewgVZBLKu9ctZfE61RU=q6oyxHAy5O_Uegs=w@mail.gmail.com' \
--to=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=pcc@google.com \
--cc=ryabinin.a.a@gmail.com \
--cc=will@kernel.org \
/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