aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/upstream-kcsan-base.config
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config/linux: regenerateTaras Madan2026-01-201-22/+47
|
* dashboard/config: regenerate Linux configsAleksandr Nogikh2026-01-151-6/+15
| | | | | No extra changes, just a newer Docker container to minimize noise in the following commits.
* dashboard: regenerate Linux configsPimyn Girgis2025-10-201-23/+32
| | | | Use v6.18-rc1 and the latest linux-next tag.
* dashboard/config/linux: regenerate filesTaras Madan2025-10-061-55/+58
|
* dashboard/config/linux: always enable GVNICAleksandr Nogikh2025-08-081-1/+6
|
* dashboard/config/linux: disable CONFIG_CGROUP_BPFAleksandr Nogikh2025-07-171-4/+4
| | | | | | | | | | It seems incredibly difficult to clean up the side effects of this kernel functionality. Keep it enabled only on a new config dedicated specifically for the snapshot-based instance. Closes #5956.
* dashboard: regenerate Linux configsAleksandr Nogikh2025-06-131-30/+48
| | | | Use v6.16-rc1 and the latest linux-next tag.
* dashboard/config/linux: add upstream-rust-kasan configAleksandr Nogikh2025-05-201-6/+10
| | | | Enable RUST as well as other Rust-related configs.
* dashboard/config: enable ANDROID_BINDERFSAleksandr Nogikh2025-04-291-4/+4
| | | | The bugs that were popping up during image tests now seem to be fixed.
* dashboard/configs: regenerate Linux configsAleksandr Nogikh2025-04-251-63/+90
| | | | Use the latest linux-next and torvalds releases.
* dashboard/config: regenerate clang configs with LLVM=1Aleksandr Nogikh2025-04-171-5/+3
|
* dashboard/config: regenerate Linux configsAleksandr Nogikh2025-03-291-37/+39
| | | | Use the latest linux-next and the latest torvalds release.
* dashboard/config/linux: enable FORTIFY_SOURCE for clangAleksandr Nogikh2025-02-131-2/+1
| | | | | It must have been fixed since Linux 5.18 and Clang 13. See #5773.
* dashboard/config/linux: update to v6.13 and latest nextAleksandr Nogikh2025-01-301-33/+81
| | | | | Remove the deprecated options. Replace old "linux-next" conditions with the version numbers.
* dashboard/config: set RCU_EXP_CPU_STALL_TIMEOUT to 0Aleksandr Nogikh2024-11-011-1/+1
| | | | | | | | The zero values makes the kernel use the RCU_CPU_STALL_TIMEOUT value, which is already set to a big enough value. Context: see the recent LKML discussion at https://lore.kernel.org/all/6723aa4d.050a0220.35b515.0161.GAE@google.com/T/
* dashboard/config/linux: increase number of devices to 32Dmitry Vyukov2024-10-241-1/+1
|
* dashboard/config: regenerate Linux configsAleksandr Nogikh2024-08-291-13/+30
| | | | | Regenerate the configs using the latest mainline, linux-next and stable versions.
* dashboard/config: enable LRU_GEN for most instancesDmitry Vyukov2024-07-101-1/+4
| | | | | It's not the default for most kernels, so it makes sense to test it more. E.g. for KCSAN, KMSAN we have only 1 instance, makes sense to test LRU_GEN.
* dashboard/config/linux: regenerate configsAleksandr Nogikh2024-06-181-12/+40
| | | | | Regenerate the configs using the latest RC and the latest linux-next tag.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2024-04-081-27/+63
| | | | | | Regenerate configs using latest Linux release candidate and linux-next. Enable more bcachefs configs.
* dashboard/configs: update linux configsAleksandr Nogikh2024-01-301-38/+90
| | | | Regenerate the configs using the latest Linux revisions.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2023-10-231-38/+89
| | | | | | | | | Use latest Linux mainline and -next versions. Disable config options that were dropped. Stop disabling PINCTRL for arm64_emu -- it's too tricky to ensure it's not enabled + it's only possible to test it on qemu anyway.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2023-07-131-6/+5
| | | | | 1) Migration to a new Docker image changed toolchain versions. 2) Regenerate cuttlefish configs that were previously omitted.
* dashboard/config: enable CONFIG_PVH for Linux/x86_64Aleksandr Nogikh2023-07-051-1/+1
| | | | This will let users boot directly from the vmlinux file.
* dashboard/config: make Linux baseline configs smallerAleksandr Nogikh2023-07-041-658/+18
| | | | Disable more kernel configs for baseline files.
* dashboard/config/linux: update to latest upstreamMarco Elver2023-06-301-33/+44
| | | | | | | | | | | | | Update mainline tag and linux-next version. Notable changes: - SLAB is being deprecated. To still be able to test it we need to set SLAB_DEPRECATED. Due to SLAB deprecation, the kcsan and leak instances are switched to SLUB to avoid tripping over issues due to SLAB not being supported properly anymore.
* dashboard/config/linux: update configs to latest kernelsDmitry Vyukov2023-04-271-21/+22
|
* dashboard/config/linux: update to latest kernelsDmitry Vyukov2023-04-031-33/+39
|
* dashboard/config/linux: update to latest kernelDmitry Vyukov2023-02-151-2/+2
|
* dashboard/linux: switch clang configs to DWARF4Aleksandr Nogikh2023-02-081-2/+2
| | | | Currently syzbot is unable to symbolize reports for DWARF5.
* dashboard/config: update linux configs with clang 15Aleksandr Nogikh2023-02-071-3/+17
|
* dashboard/config/linux: update configsAleksandr Nogikh2023-01-261-19/+48
| | | | | | | Update the configs to the latest Linux versions: v6.2-rc5 and next-20230124. Enable CONFIG_NMI_CHECK_CPU and rcupdate.rcu_cpu_stall_cputime.
* dashboard/config/linux: enable new configsDmitry Vyukov2022-11-141-1/+40
| | | | | Enable some new configs that are reachable in VMs and some new debugging configs.
* dashboard/config/linux: update upstream configsDmitry Vyukov2022-11-141-170/+267
| | | | | | | | | | | | | | | | | | | | | Update linux upstream configs to the latest mainline/linux-next tags. - RANDOM_TRUST_CPU was removed (defaults to y) - RANDOM_TRUST_BOOTLOADER was removed (defaults to y) - X86_SGX now requires X86_X2APIC - DRM_VMWGFX_FBCON was removed - ANDROID was removed - NFT_OBJREF was removed - CAN_SLCAN now requires new CAN_NETLINK - CRYPTO_BLAKE2S was split into CRYPTO_BLAKE2S_X86 and CRYPTO_BLAKE2S_ARM - DEBUG_VM_VMACACHE was removed - CONTEXT_TRACKING_FORCE was removed - DRM_DP_AUX_CHARDEV now requires DRM_I915 (or some other DRM driver) - CRYPTO_SM4 was split into x86_64 amd arm64 configs - ARM_CRYPTO was removed - BINFMT_SHARED_FLAT was removed Also update all configs that were marked as linux-next.
* dashboard/config: enable core dump configsDmitry Vyukov2022-10-071-1/+1
| | | | | | | | They are actually enabled now but merely because they are inherited from def configs. Enable them explicitly. But coredump_filter=0xffff cmd line argument is useful, it will allow to test more parts of the core dumping functionality.
* dashboard/config: enable debug options for the arm64-full configAleksandr Nogikh2022-08-051-1/+1
| | | | Also, factor emulation-dependent consts into a separate file.
* dashboard/config/linux: update configsAlexander Potapenko2022-06-021-4/+4
| | | | | | | | 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
* dashboard/config/linux: update configs to next-20220505Marco Elver2022-05-051-13/+13
| | | | Along with small changes due to changed Kconfig variables.
* dashboard/config/linux: disable MSR writesDmitry Vyukov2022-04-251-1/+1
| | | | | | | | | | | | | | | | | | Randomly changing MSRs can have unpredictable results. We tried to protect from writes on descriptions level, but it does not work well, the fuzzer has figured out: 03:37:28 executing program 3: syz_open_dev$MSR(&(0x7f0000000040), 0x0, 0x0) r0 = syz_open_procfs(0x0, &(0x7f0000000180)='fd/3\x00') pwritev(r0, ...) Fortunately there is a command line argument that disables all writes. Use it instead. Note: older kernels will need: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a7e1f67ed29f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=02a16aa13574
* dashboard/config/linux: enable CSD_LOCK_WAIT_DEBUGDmitry Vyukov2022-04-201-1/+1
| | | | | | As asked by Hillf here: https://lore.kernel.org/all/20220419134616.GE4285@paulmck-ThinkPad-P17-Gen-1/ This config can provide more precise diagnostic for some bugs.
* dashboard/config/linux: set CONFIG_WERROR=nMarco Elver2022-04-061-1/+1
| | | | | | | | | | | | | | | | | 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: regenerate configsAleksandr Nogikh2022-04-061-3/+7
| | | | | | Switch arm64 instances to clang. Enable KCOV for arm64. Regenerate configs with clang13.
* dashboard/config/linux: update linux configs to v5.18-rc1Taras Madan2022-04-061-42/+77
| | | | | update linux to v5.18-rc1 fix dependency update errors update configs
* dashboard/config: update configs to next-20220222Aleksandr Nogikh2022-02-241-1/+3
| | | | | | | | | Move CONFIG_AID_FOR_SYZBOT to verbatim since it has for some reason disappeared from the linux-next tree. Add CONFIG_RCU_EXP_CPU_STALL_TIMEOUT and set it to the maximum value. Otherwise it overwhelms syzbot with `INFO: rcu_preempt detected expedited stalls on CPUs/tasks` crashes.
* dashboard/config/linux: update upstream configsDmitry Vyukov2022-01-271-53/+114
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update mainline and linux-next revisions to the latest tags and fix configs that broke. NF_FLOW_TABLE_IPV4/6 were removed in: commit c42ba4290b2147aa033d17f22151494515655d77 netfilter: flowtable: remove ipv4/ipv6 modules CONFIG_DAX_DRIVER was removed in: commit afd586f0d06ce3d81b7c474499630fec88833828 dax: remove CONFIG_DAX_DRIVER BLK_DEV_CRYPTOLOOP was removed in: commit 47e9624616c80c9879feda536c48c6a3a0ed9835 block: remove support for cryptoloop and the xor transfer NFT_COUNTER was removed in: commit 023223dfbfb34fcc9b7dd41e21fbf9a5d5237989 netfilter: nf_tables: make counter support built-in ICST was renamed to CLK_ICST in: commit 323fd5955f844d1b6acf1a1af488da460f657ff2 clk: versatile: Rename ICST to CLK_ICST APPARMOR_INTROSPECT_POLICY was added as requirement for other configs we enabled in: commit abfb9c0725f274c75ca2a51684c2dd842a8dc254 apparmor: make export of raw binary profile to userspace optional
* dashboard/config/linux: run make configs under syz-envDmitry Vyukov2021-11-091-5/+4
| | | | | | make configs uses host compilers. This produces constant diffs in the generated configs related to different compiler versions. Suggest to run make configs under syz-env and check-in configs produced this way.
* dashboard/config/linux: enable networking subsystems for KCSAN instanceMarco Elver2021-11-091-278/+236
| | | | | | | Add the 'onlynet' tag and use it on the KCSAN instance. Strictly speaking 'wireless', 'bluetooth', and 'hamradio' could also be included in 'onlynet', but leave them out for now.
* dashboard/config: kcsan: select CONFIG_KCSAN_PERMISSIVEMarco Elver2021-09-061-0/+1
| | | | | | | | | | | | The new CONFIG_KCSAN_PERMISSIVE is now supported in mainline: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa829778b16f15266fefe2640f04931b16ce39c0 Select it in the default syzbot config. The configs were updated manually, because we should wait until v5.15-rc1 is out (mainline is still in the merge window), at which point we can update upstream's commit hash for syz-kconf and regenerate all configs.
* dashboard/config/linux: update configsDmitry Vyukov2021-04-141-3/+3
| | | | Bump kernel revisions to the latest upstream/linux-next/kmsan.
* dashboard/config/linux: disable CONFIG_PCPU_DEV_REFCNT, add ↵Dmitry Vyukov2021-03-261-1/+1
| | | | | | | | netdev_unregister_timeout_secs Disable CONFIG_PCPU_DEV_REFCNT, it should provide refcount underflow detection. Set netdev_unregister_timeout_secs to the timeout used for task hung detection, it should avoid false "unregister_netdevice: waiting for DEV to become free" crashes.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-11 19:52:10 +0000