On Sun, Feb 17, 2019 at 5:34 AM Qian Cai <c...@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 please elaborate what exactly happens and who/why kills CPUs? Number of memory accesses should not make any difference. With hardware support (MTE) it won't be possible to disable instrumentation (loads and stores check tags themselves), so it would be useful to keep track of exact reasons we disable instrumentation to know how to deal with them with hardware support. It would be useful to keep this info in the comment in the Makefile. Thanks > Signed-off-by: Qian Cai <c...@lca.pw> > --- > kernel/trace/Makefile | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/kernel/trace/Makefile b/kernel/trace/Makefile > index c2b2148bb1d2..fdd547a68385 100644 > --- a/kernel/trace/Makefile > +++ b/kernel/trace/Makefile > @@ -28,6 +28,11 @@ ifdef CONFIG_GCOV_PROFILE_FTRACE > GCOV_PROFILE := y > endif > > +# Too much pointer access will kill hwasan. > +ifdef CONFIG_KASAN_SW_TAGS > +KASAN_SANITIZE := n > +endif > + > CFLAGS_trace_benchmark.o := -I$(src) > CFLAGS_trace_events_filter.o := -I$(src) > > -- > 2.17.2 (Apple Git-113) > > -- > You received this message because you are subscribed to the Google Groups > "kasan-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kasan-dev+unsubscr...@googlegroups.com. > To post to this group, send email to kasan-...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/kasan-dev/20190217043434.46233-1-cai%40lca.pw. > For more options, visit https://groups.google.com/d/optout.
