f5d2313bd3
Previously the system would lock up if ftrace was enabled together with KCSAN. This is due to recursion on reporting if the tracer code is instrumented with KCSAN. To avoid this for all types of tracing, disable KCSAN instrumentation for all of kernel/trace. Furthermore, since KCSAN relies on udelay() to introduce delay, we have to disable ftrace for udelay() (currently done for x86) in case KCSAN is used together with lockdep and ftrace. The reason is that it may corrupt lockdep IRQ flags tracing state due to a peculiar case of recursion (details in Makefile comment). Reported-by: Qian Cai <cai@lca.pw> Tested-by: Qian Cai <cai@lca.pw> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Marco Elver <elver@google.com> Signed-off-by: Paul E. McKenney <paulmck@kernel.org> Signed-off-by: Ingo Molnar <mingo@kernel.org>
15 lines
403 B
Makefile
15 lines
403 B
Makefile
# SPDX-License-Identifier: GPL-2.0
|
|
KCSAN_SANITIZE := n
|
|
KCOV_INSTRUMENT := n
|
|
UBSAN_SANITIZE := n
|
|
|
|
CFLAGS_REMOVE_core.o = $(CC_FLAGS_FTRACE)
|
|
CFLAGS_REMOVE_debugfs.o = $(CC_FLAGS_FTRACE)
|
|
CFLAGS_REMOVE_report.o = $(CC_FLAGS_FTRACE)
|
|
|
|
CFLAGS_core.o := $(call cc-option,-fno-conserve-stack,) \
|
|
$(call cc-option,-fno-stack-protector,)
|
|
|
|
obj-y := core.o debugfs.o report.o
|
|
obj-$(CONFIG_KCSAN_SELFTEST) += test.o
|