From 53c67432e69b0df4ff64448b944cbffaecec20f4 Mon Sep 17 00:00:00 2001 From: Marco Elver Date: Wed, 6 Apr 2022 23:01:09 +0200 Subject: dashboard/config/linux: set CONFIG_WERROR=n Our Clang+KASAN instance is breaking due to CONFIG_WERROR being turned on in x86_64 defconfig [1], which in turn is used to generate our baseline configs, and therefore has accidentally been enabled in our syzbot configs as well. This issue has been discussed in great detail when CONFIG_WERROR was first introduced, with the conclusion that it is the wrong default for runtime-test focused bots [2]. Therefore, disable CONFIG_WERROR for syzbot, to not have the odd compiler warning interrupt precious fuzzing time. [1] https://lore.kernel.org/all/000000000000008dae05dbfebd85@google.com/ [2] https://git.kernel.org/torvalds/c/b339ec9c229aaf399296 --- dashboard/config/linux/bits/base.yml | 3 +++ 1 file changed, 3 insertions(+) (limited to 'dashboard/config/linux/bits') diff --git a/dashboard/config/linux/bits/base.yml b/dashboard/config/linux/bits/base.yml index 1f43036ce..c9cf71a1e 100644 --- a/dashboard/config/linux/bits/base.yml +++ b/dashboard/config/linux/bits/base.yml @@ -26,6 +26,9 @@ config: - EXPERT - DEBUG_KERNEL + # Continuous fuzzing is more important than breaking on warnings. + - WERROR: n + # panic=86400: prevents kernel from rebooting so that we don't get reboot output in all crash reports. # Huge page overcommit is disabled by default, allowing some overcommit # with vm.nr_overcommit_hugepages is intended to give more coverage. -- cgit mrf-deployment