aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/upstream-kmsan-next.config
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config/linux: regenerateTaras Madan2026-01-201-53/+105
|
* dashboard/config: regenerate Linux configsAleksandr Nogikh2026-01-151-6/+14
| | | | | No extra changes, just a newer Docker container to minimize noise in the following commits.
* dashboard: regenerate Linux configsPimyn Girgis2025-10-211-14/+2
| | | | Disable rust by default for all instance, only enabling it where it's specified.
* dashboard: regenerate Linux configsPimyn Girgis2025-10-201-51/+17
| | | | Use v6.18-rc1 and the latest linux-next tag.
* dashboard/config/linux: regenerate filesTaras Madan2025-10-061-99/+304
|
* dashboard/config/linux: disable CONFIG_CGROUP_BPFAleksandr Nogikh2025-07-171-5/+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-7/+125
| | | | | | | | | | | | | | | | | | | - 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: regenerate Linux configsAleksandr Nogikh2025-06-131-42/+65
| | | | Use v6.16-rc1 and the latest linux-next tag.
* dashboard/config/linux: add upstream-rust-kasan configAleksandr Nogikh2025-05-201-5/+9
| | | | 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/config/linux: enable SYSFS_SYSCALLAleksandr Nogikh2025-04-251-1/+1
|
* dashboard/configs: regenerate Linux configsAleksandr Nogikh2025-04-251-47/+62
| | | | Use the latest linux-next and torvalds releases.
* dashboard/config: regenerate clang configs with LLVM=1Aleksandr Nogikh2025-04-171-1/+1
|
* dashboard/config/linux: enable CONFIG_DEBUG_VFSAleksandr Nogikh2025-03-291-1/+1
| | | | | It will be available from v6.15, but we can already enable it for linux-next.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2025-03-291-74/+152
| | | | Use the latest linux-next and the latest torvalds release.
* dashboard/config/linux: disable ANDROID_BINDERFSAleksandr Nogikh2025-03-131-1/+1
| | | | | Here we go again, now a different bug: https://syzkaller.appspot.com/bug?extid=72b65b56208e052e606c
* dashboard/config/linux: reenable ANDROID_BINDERFSAleksandr Nogikh2025-03-121-1/+1
| | | | | | It is now resolved on torvalds and linux-next. Fixes #5828.
* 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: temporarily disable BINDERFSAleksandr Nogikh2025-01-301-1/+1
| | | | | 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-78/+163
| | | | | Remove the deprecated options. Replace old "linux-next" conditions with the version numbers.
* dashboard/config/linux: update configsTaras Madan2024-11-251-1/+4
| | | | Enabled CONFIG_SMB_SERVER.
* 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: disable CONFIG_KCOV_SELFTESTAleksandr Nogikh2024-09-261-1/+1
| | | | | 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/linux: regenerate configsDmitry Vyukov2024-08-301-29/+30
| | | | Regenerate deterministic configs.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2024-08-291-68/+133
| | | | | Regenerate the configs using the latest mainline, linux-next and stable versions.
* dashboard/config: regenerate configsAndrey Konovalov2024-07-251-122/+178
| | | | To enable new USB drivers from the distro configs added in the last patch.
* dashboard/config: add -next configs for KMSANAlexander Potapenko2024-07-181-0/+9506
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.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-11 20:06:46 +0000