From: Steven Rostedt <rostedt@goodmis.org>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
Ingo Molnar <mingo@redhat.com>, Qian Cai <cai@lca.pw>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] trace: skip hwasan
Date: Mon, 18 Feb 2019 12:23:22 -0500 [thread overview]
Message-ID: <20190218122322.5219d3cb@gandalf.local.home> (raw)
In-Reply-To: <CAAeHK+yDa=Ks7TY8unVfFYt7ekDOyqpqW4otyMg1XUxkFt5Q+A@mail.gmail.com>
On Mon, 18 Feb 2019 16:56:44 +0100
Andrey Konovalov <andreyknvl@google.com> wrote:
> On Mon, Feb 18, 2019 at 4:53 PM Qian Cai <cai@lca.pw> wrote:
> >
> >
> >
> > On 2/18/19 10:25 AM, Andrey Konovalov wrote:
> > > On Sun, Feb 17, 2019 at 5:34 AM Qian Cai <cai@lca.pw> wrote:
> > >>
> > >> Enabling function tracer with CONFIG_KASAN_SW_TAGS=y (hwasan) tracer
> > >> causes the whole system frozen on ThunderX2 systems with 256 CPUs,
> > >> because there is a burst of too much pointer access, and then KASAN will
> > >> dereference each byte of the shadow address for the tag checking which
> > >> will kill all the CPUs.
> > >
> > > Hi Qian,
> > >
> > > Could you check if adding "CFLAGS_REMOVE_tags.o = -pg" into
> > > mm/kasan/Makefile helps with that?
> >
> > Yes, you nailed it!
>
> Great! I'll send the patch.
OK, then I'll ignore the original patch in this thread.
-- Steve
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-02-18 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 4:34 [PATCH] trace: skip hwasan Qian Cai
2019-02-17 7:30 ` Dmitry Vyukov
2019-02-18 13:27 ` Qian Cai
2019-02-18 13:56 ` Dmitry Vyukov
2019-02-18 13:59 ` Will Deacon
2019-02-21 14:19 ` James Morse
2019-02-18 10:43 ` Will Deacon
2019-02-18 15:25 ` Andrey Konovalov
2019-02-18 15:53 ` Qian Cai
2019-02-18 15:56 ` Andrey Konovalov
2019-02-18 17:23 ` Steven Rostedt [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=20190218122322.5219d3cb@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=will.deacon@arm.com \
/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