aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/bits/subsystems.yml
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config/linux: update to v6.19-rc5Taras Madan2026-01-201-2/+4
|
* dashboard: regenerate Linux configsPimyn Girgis2025-10-201-0/+2
| | | | Use v6.18-rc1 and the latest linux-next tag.
* dashboard/config/linux: update bitsTaras Madan2025-10-061-1/+7
|
* dashboard/config/linux: enable PREEMPT_RT in one configDmitry Vyukov2025-07-281-7/+8
| | | | | | | | 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-1/+3
| | | | | | | | | | 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: add stable-6.6 configsAleksandr Nogikh2025-06-161-1/+1
|
* dashboard: regenerate Linux configsAleksandr Nogikh2025-06-131-1/+1
| | | | Use v6.16-rc1 and the latest linux-next tag.
* dashboard/config: enable ANDROID_BINDERFSAleksandr Nogikh2025-04-291-3/+1
| | | | The bugs that were popping up during image tests now seem to be fixed.
* dashboard/config/linux: enable SYSFS_SYSCALLAleksandr Nogikh2025-04-251-0/+1
|
* dashboard/configs: regenerate Linux configsAleksandr Nogikh2025-04-251-4/+5
| | | | Use the latest linux-next and torvalds releases.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2025-03-291-3/+4
| | | | Use the latest linux-next and the latest torvalds release.
* dashboard/config/linux: disable ANDROID_BINDERFSAleksandr Nogikh2025-03-131-1/+3
| | | | | Here we go again, now a different bug: https://syzkaller.appspot.com/bug?extid=72b65b56208e052e606c
* dashboard/config/linux: reenable ANDROID_BINDERFSAleksandr Nogikh2025-03-121-3/+1
| | | | | | It is now resolved on torvalds and linux-next. Fixes #5828.
* dashboard/config/linux/bits: enable arch specific configs for riscvAlexandre Ghiti2025-02-131-9/+9
| | | | | kexec, memory hotplug/remove and THP features depend on architecture specific code, so let's exercise this for riscv.
* dashboard/config/linux: temporarily disable BINDERFSAleksandr Nogikh2025-01-301-1/+3
| | | | | It's currently broken even in torvalds, so if we don't disable it for some time we risk not updating all kernel images for several more weeks.
* dashboard/config/linux: update to v6.13 and latest nextAleksandr Nogikh2025-01-301-8/+12
| | | | | Remove the deprecated options. Replace old "linux-next" conditions with the version numbers.
* dashboard/config/linux: enable SMB_SERVERTaras Madan2024-11-251-0/+1
|
* dashboard/config: enable LRU_GEN for most instancesDmitry Vyukov2024-07-101-8/+0
| | | | | 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-2/+2
| | | | | Regenerate the configs using the latest RC and the latest linux-next tag.
* dashboard/config: add upstream-arm64-kasan_sw-kcov.configAlexander Potapenko2024-06-111-1/+1
| | | | | 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: regenerate Linux configsAleksandr Nogikh2024-04-081-2/+5
| | | | | | Regenerate configs using latest Linux release candidate and linux-next. Enable more bcachefs configs.
* dashboard/configs: update linux configsAleksandr Nogikh2024-01-301-7/+8
| | | | Regenerate the configs using the latest Linux revisions.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2023-10-231-11/+13
| | | | | | | | | 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: add config with unmaintained partsAleksandr Nogikh2023-10-191-1/+0
| | | | | | 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: enable CONFIG_ZSWAP_DEFAULT_ONAleksandr Nogikh2023-06-151-0/+1
|
* dashboard/config/linux: enable IOMMU/DMA configsDmitry Vyukov2023-04-271-2/+6
| | | | It seems we can cover them in qemu.
* dashboard/config/linux: update configs to latest kernelsDmitry Vyukov2023-04-271-1/+1
|
* dashboard/config/linux: enable Intel CET+LAMDmitry Vyukov2023-04-031-0/+2
| | | | Technologies we want to use and test if available.
* dashboard/config/linux: update to latest kernelsDmitry Vyukov2023-04-031-4/+4
|
* dashboard/config/linux: enable LRU_GEN on some instancesDmitry Vyukov2023-02-151-0/+8
| | | | | As requested here: https://lore.kernel.org/linux-mm/20230215015231.3646-1-hdanton@sina.com/
* dashboard/config/linux: update configsAleksandr Nogikh2023-01-261-1/+2
| | | | | | | 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: disable VFIO_CONTAINERDmitry Vyukov2022-11-141-1/+2
| | | | | As suggested by Jason Gunthorpe here: https://github.com/google/syzkaller/pull/3521#discussion_r1021644055
* dashboard/config/linux: enable new configsDmitry Vyukov2022-11-141-0/+11
| | | | | Enable some new configs that are reachable in VMs and some new debugging configs.
* dashboard/config/linux: update upstream configsDmitry Vyukov2022-11-141-6/+11
| | | | | | | | | | | | | | | | | | | | | 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-0/+4
| | | | | | | | 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/linux: update configs to next-20220505Marco Elver2022-05-051-0/+3
| | | | Along with small changes due to changed Kconfig variables.
* dashboard/config/linux: update linux configs to v5.18-rc1Taras Madan2022-04-061-5/+10
| | | | | update linux to v5.18-rc1 fix dependency update errors update configs
* dashboard/config/linux: enable TRANSPARENT_HUGEPAGE_MADVISEDmitry Vyukov2022-02-171-0/+1
| | | | | | This functionality is perfectly reachable for us via madvise. Reported-by: Brad Spengler
* dashboard/config/linux: disable deprecated FB configsDmitry Vyukov2022-01-311-6/+11
| | | | | Update FD/DRM configs based on Daniel recommendations here: https://lore.kernel.org/all/YfJ9yWW+MH8N4r4A@phenom.ffwll.local/
* dashboard/config/linux: enable ANON_VMA_NAME and DAMON_RECLAIMDmitry Vyukov2022-01-271-0/+2
| | | | Enable new configs in v5.17 that look interesting to us.
* dashboard/config/linux: update upstream configsDmitry Vyukov2022-01-271-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: fix sybsystems.yml, DAMON supportTaras Madan2021-12-271-3/+3
|
* sys/linux: add Damon descriptionshatoboar2021-12-201-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | * sys/linux/damon.txt: initial description description of DAMON's interface mounted in debugfs: target_ids, attrs, init_regions, monitor_on * sys/linux/damon.txt: additional damon interface description added added DAMON interface descriptions for schemes, kdamond_pid, mk_contexts, rm_contexts prefix of all the files with damon to avoid colliding naming * sys/linux/damon.txt: standard copyright statement added * sys/linux/damon.txt.const: const file of sys/linux/damon.txt added * sys/linux/damon.txt: type fix of pid to fmt * dashboard/config/linux/bits/subsystems.yml: damon configs added for Syzbot * dashboard/config/linux: generated kernel configs with added damon config * sys/linux/damon.txt: fmt type fix * sys/linux/damon.txt: read and close syscalls removed write and read mk_contexts summarized into one syscall some refining of syscall interfaces
* dashboard/config/linux: refactor networking configs into net.ymlMarco Elver2021-11-091-513/+0
| | | | | Move most networking related configs to net.yml, including net drivers that are dependencies for various features.
* dashboard/config/linux: update configs to 5.15Marco Elver2021-11-091-1/+1
| | | | | | | 5.15 was released, update a few TODOs that were dependent on 5.15 being properly released. Re-generate all configs.
* dashboard/config: enable binderfsAleksandr Nogikh2021-10-291-6/+4
| | | | | | Also, create only 2 binder devices at binderfs creation - we don't need 32 devices anymore, as a separate binderfs instance is now created per each syz-executor.
* dashboard/config/linux: enable SCHED_COREDmitry Vyukov2021-10-131-0/+1
|
* dashboard/config/linux: update to lateest kernelsDmitry Vyukov2021-10-131-2/+2
| | | | | | Update to latest upstream, linux-next and kmsan. KMSAN stopped supporting few configs which depend on crypto and heap auto-init.
* dashboard/config/linux: mark configs removed from 5.14Marco Elver2021-09-071-1/+1
| | | | | | RAW_DRIVER: https://git.kernel.org/torvalds/c/603e4922f1c81fc2ed3a87b4f91a8d3aafc7e093 CAIF_HSI: https://git.kernel.org/torvalds/c/ca75bcf0a83b6cc7f53a593d98ec7121c4839b43 WWAN_CORE: https://git.kernel.org/torvalds/c/89212e160b81e778f829b89743570665810e3b13
* dashboard/config/linux: config DRM_FBDEV_EMULATION is required by ↵Marco Elver2021-09-071-0/+1
| | | | | | | | | DRM_VMWGFX_FBCON As of [1] DRM_VMWGFX_FBCON depends on DRM_FBDEV_EMULATION. It doesn't hurt to always enable it also on older kernels. [1] https://git.kernel.org/torvalds/c/5dbf2fc587cb79cb366bd6e79ac6b52269d64fc5
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-11 21:28:23 +0000