From: Catalin Marinas <catalin.marinas@arm.com>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
kasan-dev <kasan-dev@googlegroups.com>,
Will Deacon <will@kernel.org>
Subject: Re: arm64 KASAN_HW_TAGS panic on non-MTE hardware on 5.12-rc1
Date: Sat, 6 Mar 2021 12:01:23 +0000 [thread overview]
Message-ID: <20210306120121.GA2932@arm.com> (raw)
In-Reply-To: <CAAeHK+ykdwBXETF5WkrWnbzzS6RAJdmqZ3DrFdM_7FoXZR3Wqg@mail.gmail.com>
On Fri, Mar 05, 2021 at 07:36:22PM +0100, Andrey Konovalov wrote:
> On Fri, Mar 5, 2021 at 6:52 PM Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > > This is weird. kasan_unpoison_task_stack() is only defined when
> > > > CONFIG_KASAN_STACK is enabled, which shouldn't be enablable for
> > > > HW_TAGS.
> > >
> > > CONFIG_KASAN=y
> > > # CONFIG_KASAN_GENERIC is not set
> > > CONFIG_KASAN_HW_TAGS=y
> > > CONFIG_KASAN_STACK=1
> >
> > From Kconfig:
> >
> > config KASAN_STACK
> > int
> > default 1 if KASAN_STACK_ENABLE || CC_IS_GCC
> > default 0
> >
> > and I use gcc.
>
> Ah, that explains it.
>
> Could you try applying this patch and see if it fixes the issue?
>
> https://patchwork.kernel.org/project/linux-mm/patch/20210226012531.29231-1-walter-zh.wu@mediatek.com/
Walter's patches already in -next fix this issue.
Thanks.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-06 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 17:11 arm64 KASAN_HW_TAGS panic on non-MTE hardware on 5.12-rc1 Catalin Marinas
2021-03-05 17:27 ` Andrey Konovalov
[not found] ` <20210305175124.GG23855@arm.com>
2021-03-05 17:52 ` Catalin Marinas
2021-03-05 18:36 ` Andrey Konovalov
2021-03-06 12:01 ` Catalin Marinas [this message]
2021-03-08 14:56 ` Andrey Konovalov
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=20210306120121.GA2932@arm.com \
--to=catalin.marinas@arm.com \
--cc=andreyknvl@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=vincenzo.frascino@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.