aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/bits/kmsan.yml
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config/linux: update to v6.19-rc5Taras Madan2026-01-201-4/+6
|
* dashboard/config: switch KMSAN configs to upstream treeAlexander Potapenko2023-08-021-4/+0
| | | | | Since we are using the upstream tree to build KMSAN on syzbot, switch the kernel configs to also reference that tree.
* dashboard/config: enable virtualization configs for KMSANAleksandr Nogikh2023-07-051-2/+0
| | | | This also lets us enable CONFIG_PVH for it.
* dashboard/config/linux: disable CONFIG_STACKPROTECTOR for KMSANAlexander Potapenko2023-05-091-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | Linux v6.4-rc1 built with Clang versions <= 16 with stack protector enabled panic with the following stack trace: Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: start_kernel+0xd8a/0xd90 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.3.0-rc1-00042-g9ea7e6b62c2b-dirty #106 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 dump_stack_lvl+0x1bc/0x250 lib/dump_stack.c:106 dump_stack+0x1e/0x20 lib/dump_stack.c:113 panic+0x4cd/0xc10 kernel/panic.c:340 __stack_chk_fail+0x18/0x20 kernel/panic.c:759 start_kernel+0xd8a/0xd90 init/main.c:? x86_64_start_reservations+0x2e/0x30 arch/x86/kernel/head64.c:556 x86_64_start_kernel+0x118/0x120 arch/x86/kernel/head64.c:537 secondary_startup_64_no_verify+0xcf/0xdb arch/x86/kernel/head_64.S:358 </TASK> https://github.com/ClangBuiltLinux/linux/issues/1815 describes the problem, which is fixed on the Clang side (https://reviews.llvm.org/D147975), but before the fix reaches syzbot we'll have to keep the stack protector disabled.
* dashboard/config/linux: enable CONFIG_KMSAN_CHECK_PARAM_RETVAL for KMSANAlexander Potapenko2023-02-201-0/+1
| | | | | Not sure why this wasn't done before, but KMSAN_CHECK_PARAM_RETVAL is quite important for KMSAN. Enable it.
* dashboard/linux: switch clang configs to DWARF4Aleksandr Nogikh2023-02-081-6/+0
| | | | Currently syzbot is unable to symbolize reports for DWARF5.
* dashboard/config/linux: switch KMSAN bots to clang-15, update configsAlexander Potapenko2023-02-071-2/+2
| | | | | | clang-15 in our Docker containers is fresh enough to use it instead of clang-kmsan. This patch also updates kmsan.yml to exclude all hardware-accelerated configs under KMSAN, as they are unsupported.
* dashboard/config/linux: enforce DWARF4 for KMSANAlexander Potapenko2022-06-141-0/+6
| | | | | Newer toolchaings generate DWARF5 by default, which might be problematic for binutils on syzbot. Use DWARF4 instead.
* dashboard/config/linux: update configsAlexander Potapenko2022-06-021-1/+3
| | | | | | | | 1. Bump KMSAN version to v5.18-rc4 Also switch to using clang-kmsan provided by syz-env. 2. Bump Linux version to v5.18 3. Bump linux-next version to next-20220601 Also enable DEBUG_NET for linux-next
* kmsan: change panic_on_kmsan=1 to kmsan.panic=1Alexander Potapenko2021-11-191-1/+1
| | | | | | This is how the boot-time parameter is called now. Signed-off-by: Alexander Potapenko <glider@google.com>
* dashboard/config/linux: update to lateest kernelsDmitry Vyukov2021-10-131-1/+1
| | | | | | Update to latest upstream, linux-next and kmsan. KMSAN stopped supporting few configs which depend on crypto and heap auto-init.
* kmsan: enable panic_on_kmsan=1Alexander Potapenko2021-06-151-0/+2
| | | | Signed-off-by: Alexander Potapenko <glider@google.com>
* dashboard/config/linux: update configsDmitry Vyukov2021-04-141-1/+1
| | | | Bump kernel revisions to the latest upstream/linux-next/kmsan.
* dashboard/config/linux: update KMSAN configDmitry Vyukov2021-02-111-1/+1
| | | | Update KMSAN config to the lastest version on top of kmsan-v5.11-rc7.
* dashboard/config/linux: update to v5.11-rc11Dmitry Vyukov2020-12-291-1/+1
| | | | Also bump KMSAN to latest kmsan-v5.10-rc4.
* dashboard/config/linux: set more configs explicitlyDmitry Vyukov2020-10-211-0/+5
| | | | | | | Next change will make fewer configs enabled implicitly, so make more configs explicit in preparation. Update #2171
* dashboard/config/linux: resolve TODOsDmitry Vyukov2020-10-211-42/+0
| | | | | | | Resolve all TODOs that were left during the switch from old to new configs to minimize diffs. Update #2171
* dashboard/config/linux: add config fragmentsDmitry Vyukov2020-10-211-0/+135
Add config fragments for the new config generation system. Update #2171