aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/bits
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config/linux: enable more configsTaras Madan2026-01-202-0/+5
| | | | | | 1. DEBUG_GENERIC_PT. 2. DEBUG_XARRAY. 3. PHY_GOOGLE_USB.
* dashboard/config/linux/bits: enable DEBUG_BUGVERBOSE_DETAILEDTaras Madan2026-01-201-0/+1
| | | | Closes #6595.
* dashboard/config/linux: update to v6.19-rc5Taras Madan2026-01-2011-18/+33
|
* dashboard/config: update Android 6.12Aleksandr Nogikh2026-01-153-2/+3
| | | | | | Use the latest available revision and disable ANDROID_BINDER_IPC - as of now, it's no longer possible to compile in both C and Rust versions at the same time.
* dashboard: enable ext4 in base configPimyn Girgis2025-10-222-4/+5
| | | | Ext4 is necessary for normal boot, enable it unconditionally in base.
* dashboard: regenerate Linux configsPimyn Girgis2025-10-212-1/+4
| | | | Disable rust by default for all instance, only enabling it where it's specified.
* dashboard: regenerate Linux configsPimyn Girgis2025-10-2011-22/+37
| | | | Use v6.18-rc1 and the latest linux-next tag.
* dashboard/config/linux: update bitsTaras Madan2025-10-066-45/+84
|
* dashboard/config/linux: update to v6.17Taras Madan2025-10-062-2/+2
|
* dashboard/config/linux: always enable GVNICAleksandr Nogikh2025-08-083-1/+4
|
* dashboard/config/linux: enable PREEMPT_RT in one configDmitry Vyukov2025-07-282-9/+10
| | | | | | | | 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-172-2/+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/config: regenerate configs to expand COMEDI fuzzingfellair2025-07-031-0/+84
| | | | | | | | | | | | | | | | | | | - 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: regenerate Android 6.12 configsAleksandr Nogikh2025-06-182-1/+5
| | | | Now that Rust Binder has been merged into the tree, we can enable it.
* dashboard/config: add stable-6.6 configsAleksandr Nogikh2025-06-164-3/+9
|
* dashboard/config/linux: drop stable-5.10Aleksandr Nogikh2025-06-161-6/+0
| | | | We haven't been fuzzing it on syzbot for a very long time.
* dashboard: regenerate Linux configsAleksandr Nogikh2025-06-136-11/+26
| | | | Use v6.16-rc1 and the latest linux-next tag.
* dashboard/config/linux: add upstream-rust-kasan configAleksandr Nogikh2025-05-201-0/+11
| | | | Enable RUST as well as other Rust-related configs.
* 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: set SERIAL_8250_RUNTIME_UARTS=4Aleksandr Nogikh2025-04-281-0/+2
| | | | | | | | | A config bisection between our LTS and Android configs have pointed to the SERIAL_8250_RUNTIME_UARTS option determining whether the kernel will hang during boot in qemu. Set SERIAL_8250_RUNTIME_UARTS=4 on our Android kernels to make them bootable.
* dashboard/config/linux: enable SYSFS_SYSCALLAleksandr Nogikh2025-04-251-0/+1
|
* dashboard/configs: regenerate Linux configsAleksandr Nogikh2025-04-258-17/+19
| | | | Use the latest linux-next and torvalds releases.
* dashboard/config: add an android-6.12 configAleksandr Nogikh2025-04-232-3/+18
|
* dashboard/config: drop COS configsAleksandr Nogikh2025-04-233-22/+1
| | | | We don't use these on syzbot.
* dashboard/config: regenerate clang configs with LLVM=1Aleksandr Nogikh2025-04-171-2/+3
|
* dashboard/config/linux: add allyes configDmitry Vyukov2025-04-152-0/+138
| | | | | Maximum config that still builds/boots. This is useful for descriptions/interface auto-extraction.
* dashboard/config/linux: enable CONFIG_DEBUG_VFSAleksandr Nogikh2025-03-291-0/+3
| | | | | It will be available from v6.15, but we can already enable it for linux-next.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2025-03-297-16/+39
| | | | 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: enable FORTIFY_SOURCE for clangAleksandr Nogikh2025-02-131-1/+1
| | | | | It must have been fixed since Linux 5.18 and Clang 13. See #5773.
* 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/bits: reenable KASAN_INLINE for riscv64Alexandre Ghiti2025-02-131-2/+1
| | | | | | | | | | | KASAN_INLINE was fixed back in early 2023 in the riscv kernel, see merge commit 2667e3673f70 ("Merge patch series "RISC-V kasan rework"). It happens that the riscv configuration was already using KASAN_INLINE so this is simply a cleanup. Since this is my first commit in syzkaller, I also added myself and Rivos in the AUTHORS/CONTRIBUTORS files.
* 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-308-24/+33
| | | | | 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: set RCU_EXP_CPU_STALL_TIMEOUT to 0Aleksandr Nogikh2024-11-012-9/+4
| | | | | | | | 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-243-3/+3
|
* dashboard: disable CONFIG_KCOV_SELFTESTAleksandr Nogikh2024-09-261-1/+4
| | | | | The kernel is not able to pass the test at the moment. See: https://lore.kernel.org/all/66eb52dc.050a0220.92ef1.0006.GAE@google.com/T/
* dashboard/config: restore CMDLINE_FROM_BOOTLOADER on arm64Aleksandr Nogikh2024-09-131-0/+2
| | | | | | It seems to have caused boot problems on ci-upstream-gce-arm64. Reported-by: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
* dashboard/config/linux: bump lockdep consts even moreDmitry Vyukov2024-08-301-4/+6
| | | | | Btrfs needs higher values to avoid false positives: https://lore.kernel.org/all/20240821201338.GA2109582@perftesting/
* dashboard/config: regenerate Linux configsAleksandr Nogikh2024-08-2912-14/+23
| | | | | Regenerate the configs using the latest mainline, linux-next and stable versions.
* dashboard/config: add -next configs for KMSANAlexander Potapenko2024-07-181-1/+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: enable LRU_GEN for most instancesDmitry Vyukov2024-07-102-8/+8
| | | | | 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-185-6/+6
| | | | | Regenerate the configs using the latest RC and the latest linux-next tag.
* dashboard/config: add upstream-arm64-kasan_sw-kcov.configAlexander Potapenko2024-06-112-1/+7
| | | | | 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: disable CONFIG_FRAME_WARN on ChromeOSAleksandr Nogikh2024-05-071-0/+2
| | | | As suggested by @groeck.
* dashboard/config: update ChromeOS configsAleksandr Nogikh2024-05-037-11/+25
| | | | | | | 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: regenerate Linux configsAleksandr Nogikh2024-04-087-9/+15
| | | | | | Regenerate configs using latest Linux release candidate and linux-next. Enable more bcachefs configs.
* dashboard/config: temporarily disable CONFIG_DEBUG_LIST for KMSANAlexander Potapenko2024-02-151-1/+2
| | | | | | | KMSAN is currently reporting boot-time false positives in debugging code called from stackdepot.c (see https://github.com/google/syzkaller/issues/4504) Disable CONFIG_DEBUG_LIST under KMSAN until the fix lands.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-11 21:11:31 +0000