summaryrefslogtreecommitdiff
path: root/kernel/sched/Makefile
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2020-05-04 15:25:30 +0200
committerThomas Gleixner <tglx@linutronix.de>2020-05-04 15:25:30 +0200
commita8644aebec1152b992d5d54a05a538d338262944 (patch)
tree5c0084fbcaf77545497d0ca92bc033693b185653 /kernel/sched/Makefile
parent9e96e646e6f890308110cb7c81f200f5211cf082 (diff)
parent3b02a051d25d9600e9d403ad3043aed7de00160e (diff)
Merge branch 'locking/kcsan' into x86/entryentry-base
Pull the pending KCSAN changes as the required changes vs. atomics to fixup INT3 interfere with the KCSAN modifications of atomics.
Diffstat (limited to 'kernel/sched/Makefile')
-rw-r--r--kernel/sched/Makefile6
1 files changed, 6 insertions, 0 deletions
diff --git a/kernel/sched/Makefile b/kernel/sched/Makefile
index 21fb5a5662b5..5fc9c9b70862 100644
--- a/kernel/sched/Makefile
+++ b/kernel/sched/Makefile
@@ -7,6 +7,12 @@ endif
# that is not a function of syscall inputs. E.g. involuntary context switches.
KCOV_INSTRUMENT := n
+# There are numerous data races here, however, most of them are due to plain accesses.
+# This would make it even harder for syzbot to find reproducers, because these
+# bugs trigger without specific input. Disable by default, but should re-enable
+# eventually.
+KCSAN_SANITIZE := n
+
ifneq ($(CONFIG_SCHED_OMIT_FRAME_POINTER),y)
# According to Alan Modra <alan@linuxcare.com.au>, the -fno-omit-frame-pointer is
# needed for x86 only. Why this used to be enabled for all architectures is beyond