aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/main.yml
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config/linux: enable PREEMPT_RT in one configDmitry Vyukov2025-07-281-1/+1
| | | | | | | | To get coverage of PREEMPT_RT as well. The disabled configs are marked as incompatible with PREEMPT_RT in Kconfig files. Fixes #6225
* dashboard/config/linux: disable CONFIG_CGROUP_BPFAleksandr Nogikh2025-07-171-0/+1
| | | | | | | | | | 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/config: regenerate configs to expand COMEDI fuzzingfellair2025-07-031-0/+1
| | | | | | | | | | | | | | | | | | | - Add comedi.yml fragment with all usb and manually configurable legacy comedi drivers. Specify x86_64-only setting for drivers that depend on CONFIG_ISA[_BUS]. - Set the comedi.comedi_num_legacy_minors=4 kernel config param. That way there are always /dev/comediN devices to try COMEDI_DEFCONFIG ioctl on. - Enable comedi.yml fragment for most instances. Disable it for ChromeOS and Android, as well as some other arches to avoid conflicts. This change will disable some already set COMEDI config options (like COMEDI usb drivers) in a few instances. It should not adversely affect overall coverage as most other instances will keep those options and add more on top.
* dashboard/config: add stable-6.6 configsAleksandr Nogikh2025-06-161-0/+3
|
* dashboard/config/linux: drop stable-5.10Aleksandr Nogikh2025-06-161-5/+0
| | | | We haven't been fuzzing it on syzbot for a very long time.
* dashboard/config/linux: add upstream-rust-kasan configAleksandr Nogikh2025-05-201-1/+3
| | | | Enable RUST as well as other Rust-related configs.
* dashboard/config: add an android-6.12 configAleksandr Nogikh2025-04-231-0/+2
|
* dashboard/config: drop COS configsAleksandr Nogikh2025-04-231-6/+0
| | | | We don't use these on syzbot.
* dashboard/config/linux: add allyes configDmitry Vyukov2025-04-151-0/+2
| | | | | Maximum config that still builds/boots. This is useful for descriptions/interface auto-extraction.
* dashboard/config: drop security modules bits from usb instanceAndrey Konovalov2024-07-231-1/+1
| | | | | | | | | | | | | | | | | | | | | CONFIG_SECURITY_TOMOYO produces a large amount of coverage entries for each ioctl call. For normal instances, this might not be a problem, as they call only a single ioctl for each syzkaller syscall. However, the syz_usb_connect pseudo-syscall calls a large number of ioctls. As a result, the KCOV coverage buffer for this syscall might overflow due to the tomoyo-produced entries. For example, with tomoyo, the first syscall of the vusb_ath9k runtest produces ~140k KCOV entries (with [1] applied), which is not far from the current 256k limit of KCOV entries per syscall. With tomoyo disabled, the number of entries falls to ~30k. Drop the security modules–related bits from the USB instance: I don't think they are useful for that instance anyway. [1] https://lore.kernel.org/all/eaf54b8634970b73552dcd38bf9be6ef55238c10.1718092070.git.dvyukov@google.com/
* dashboard/config: add -next configs for KMSANAlexander Potapenko2024-07-181-0/+1
| | | | | | | | We are going to replace ci-upstream-kmsan-gce-386-root with an x86_64 instance tracking -next. The new configs will be using smack instead of AppArmor to increase the overall KMSAN coverage.
* dashboard/config: add upstream-arm64-kasan_sw-kcov.configAlexander Potapenko2024-06-111-0/+2
| | | | | The new config will enable KASAN_SW_TAGS and KCOV. Also make sure KVM_SW_PROTECTED_VM is only enabled on x86_64.
* dashboard/config: update ChromeOS configsAleksandr Nogikh2024-05-031-5/+5
| | | | | | | Use the latest revisions for existing configs. Add the new ChromeOS 6.6 config. No longer generate ChromeOS 5.4 configs. Switch ChromeOS configs to clang.
* dashboard/config: use clang for upstream-apparmor-kasan.configAleksandr Nogikh2024-02-011-1/+1
|
* dashboard/configs: update linux configsAleksandr Nogikh2024-01-301-2/+1
| | | | Regenerate the configs using the latest Linux revisions.
* dashboard: disable CONFIG_BLK_DEV_WRITE_MOUNTEDAleksandr Nogikh2023-11-131-0/+1
| | | | | | | This has become possible with the new series from Jan Kara: https://lore.kernel.org/all/20231101173542.23597-1-jack@suse.cz/ Regenerate configs on the latest linux-next.
* dashboard/config: add config with unmaintained partsAleksandr Nogikh2023-10-191-0/+2
| | | | | | Disable unmaintained code parts (at least those known so far) in existing configs and enable them in a special upstream-unmaintained.config file.
* dashboard/config: switch KMSAN configs to upstream treeAlexander Potapenko2023-08-021-1/+1
| | | | | Since we are using the upstream tree to build KMSAN on syzbot, switch the kernel configs to also reference that tree.
* dashboard/config: generate Linux 5.10 LTS configsAleksandr Nogikh2023-07-071-0/+3
|
* dashboard/config: make Linux baseline configs smallerAleksandr Nogikh2023-07-041-0/+1
| | | | Disable more kernel configs for baseline files.
* dashboard/config/linux: update to latest upstreamMarco Elver2023-06-301-2/+2
| | | | | | | | | | | | | 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: introduce upstream-kasan-badwrites.configMarco Elver2023-06-301-0/+2
| | | | | | | | | | | | | | | | | Introduce a variant of upstream-apparmor-kasan, which enables: - kasan.fault=panic_on_write [1] - kasan_multi_shot, so that panic_on_warn does cause KASAN to panic on bad non-write accesses As discussed in [1], "KASAN reported invalid _writes_ are of special interest, because they have greater potential to corrupt random kernel memory or be more easily exploited." With this config we can set up a syzbot instance that can detect such issues. [1] https://lore.kernel.org/linux-mm/20230614095158.1133673-1-elver@google.com/
* dashboard/config, tools/syz-kconf: add Cuttlefish supportLiz Prucka2023-06-291-0/+4
| | | | | | | Allow modules in config if `modules` are specified in main.yml. Added Cuttlefish instances for android13-5.10, android13-5.15, and android14-5.15 branches.
* dashboard: add ChromeOS 6.1 configs (#3932)Aleksandr Nogikh2023-06-011-0/+2
|
* dashboard: add COS-6.1 configsAleksandr Nogikh2023-05-301-0/+3
|
* dashboard/config/linux: add support for Android 6.1Tudor Ambarus2023-05-041-0/+2
| | | | | | | Add support for Android 6.1. The configs are for 'android14-6.1', there's no android-6.1-lts available yet. Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
* dashboard/config: add configs for v5.15 and v6.1Aleksandr Nogikh2023-03-071-0/+6
| | | | | We are currently testing lts branches which are already too old. Add configs for the more relevant stable versions.
* dashboard/config: generate COS 5.15 configs for fuzzingAleksandr Nogikh2023-02-201-0/+3
|
* dashboard/config: split arm64.yml into base and -emu partsAleksandr Nogikh2023-02-201-2/+3
| | | | | | Most of the arm64.yml tweaks were actually needed to fuzz Linux on qemu. Now that we can also fuzz it in the non-emulated environment, let's split it into the base arm64 settings and the settings needed for qemu.
* dashboard/config/linux: enable DWARF4 for allDmitry Vyukov2023-02-181-1/+0
|
* dashboard/config: enable KASAN and KFENCE for upstream-arm64-fullAleksandr Nogikh2023-02-131-1/+1
|
* dashboard/linux: switch clang configs to DWARF4Aleksandr Nogikh2023-02-081-0/+1
| | | | Currently syzbot is unable to symbolize reports for DWARF5.
* dashboard/config/linux: update configsAleksandr Nogikh2023-01-261-1/+1
| | | | | | | 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: fold android-5.10-late.yml into android-5.10.ymlSpace Meyer2022-11-141-1/+0
| | | | Due to PR #3513 we no longer need the -late.yml
* syz-kconf: execute shell snippets in reverse loading orderSpace Meyer2022-11-091-10/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Background: - syz-kconf loads and overlays config fragments to form a final kernel config. Fragments are loaded top to bottom as defined in the includes section of main.yml or your downstream syz-kconf config. - A config fragment loaded later can override kconf options set by an earlier loaded fragment. However the override keyword can only be used if an earlier fragment really did set the same option. Otherweise an error is raised. - With this in mind it makes sense to load fragments from broadest scope to most specific e.g. base -> x86_64 -> chromeos, so that chromeos can override a setting usually enabled on x86_64 machines. The Problem: - Before this change shell snippets were executed in order they were loaded from the fragments. - This is unfortunate as the broad fragments like x86_64.yml expect to operate on an existing .config with their shell snippets. Meanwhile some downstream distros like icebreaker generate their config using such a shell snippet. - Hence ordering the fragments like base -> x86_64 -> icebreaker results in an error about the x86_64 not finding a .config without this change. Meanwhile ordering icebreaker -> base -> x86_64 works, but means the icebreaker fragment can't override x86_64 kconf options. The Solution: - This change resolves the problem outlined above by reversing the order shell snippets are executed. Now shell snippets will be executed starting with the most recently loaded fragment. This way the proposed fragment order base -> x86_64 -> icebreaker becomes viable. - Luckily the shell section isn't heavily used, so this change didn't result in meaningfull final config changes.
* dashboard/config/linux: add support for Android v5.15Tadeusz Struk2022-10-041-0/+2
| | | | | | | | | | | | The tag that is provided is from 'android13-5.15-lts'. The LTS version must be used, as it is more up-to-date in terms of security fixes and stable back-ports than its non-lts counterpart. Using a tag from the non-lts branch will result in lots of false positives which would end up wasting quality engineering time. Signed-off-by: Tadeusz Struk <tadeusz.struk@linaro.org>
* dashboard/config: enable debug options for the arm64-full configAleksandr Nogikh2022-08-051-19/+21
| | | | Also, factor emulation-dependent consts into a separate file.
* dashboard: regenerate configsAleksandr Nogikh2022-04-061-3/+3
| | | | | | Switch arm64 instances to clang. Enable KCOV for arm64. Regenerate configs with clang13.
* dashboard/config/linux: disable IO_URING for android 5.10Dmitry Vyukov2022-03-051-0/+1
|
* dashboard/config/linux: add arm/arm64 full configsDmitry Vyukov2022-01-131-0/+3
| | | | | | We generate slightly reduces configs for arm/arm64 b/c we test in slow qemu VMs. Add full versions of these configs that can be used with syz-check to avoid no-such-struct warnings.
* dashboard/config: add ChromeOS 5.15 support (#2948)Taras Madan2021-12-291-0/+2
| | | | To add the ChromeOS 5.15 configs. It required to disable the INCREMENTAL_FS support.
* dashboard/config: add chromeos-5.10 support (#2947)Taras Madan2021-12-271-0/+2
| | | To add the ChromeOS 5.10 support.
* dashboard/config/linux: disable lockdep on armMarco Elver2021-11-091-1/+2
| | | | | | | | | | | | | | | The arm instance has been broken since ~March this year because lockdep appears broken on arm [1]. Unfortunately it hasn't been fixed since, and it is unclear if this is going to happen soon. Since this is holding up fuzzing on arm, and generally causing dozens of fixes to still appear as "fix pending" on the syzbot dashboard, simply disable lockdep on the arm instance. This will allow to at least make some progress and find bugs with the remaining configs on the arm instance. [1] https://lore.kernel.org/all/0000000000004f14c105bde08f75@google.com/
* dashboard/config/linux: simplify debug.yml and lockdep.yml constraintsMarco Elver2021-11-091-2/+2
| | | | | | Simplify contraints on debug.yml and lockdep.yml: kmsan, kcsan, and kmemleak instances already list nonoise, so there's no point in adding these constraints to debug.yml and lockdep.yml.
* dashboard/config/linux: refactor lockdep configs into lockdep.ymlMarco Elver2021-11-091-0/+1
| | | | | | All of lockdep comes with a number of config options, so let's refactor it into a separate lockdep.yml, which makes it easier to disable selectively.
* dashboard/config/linux: enable networking subsystems for KCSAN instanceMarco Elver2021-11-091-10/+10
| | | | | | | 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/linux: refactor networking configs into net.ymlMarco Elver2021-11-091-0/+1
| | | | | Move most networking related configs to net.yml, including net drivers that are dependencies for various features.
* dashboard/config/linux: rename subsystems_net to net-extraMarco Elver2021-11-091-1/+1
|
* dashboard/config/linux: add support for Android v5.10Lee Jones2021-10-201-0/+2
| | | | | | | | | | | | The tag that is provided is from 'android12-5.10-lts'. The LTS version must be used, as it is more up-to-date in terms of security fixes and stable back-ports than its non-lts counterpart. Using a tag from the non-lts branch will result in lots of false positives which would end up wasting quality engineering time. Signed-off-by: Lee Jones <lee.jones@linaro.org>
* Revert "dashboard/config/linux: disable -Werror on clang instances"Marco Elver2021-09-081-1/+0
| | | | | | | | | | | This reverts commit e096c0a2a414e487412c9669426780ce5acdde9d. After a long discussion [1], Linus decided to default WERROR to COMPILE_TEST [2]. This means we no longer have to unset the option explicitly. [1] https://lkml.kernel.org/r/YTfkO2PdnBXQXvsm@elver.google.com [2] https://git.kernel.org/torvalds/c/b339ec9c229aaf399296a120d7be0e34fbc355ca
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-22 10:48:57 +0000