aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/upstream-leak.config
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config/linux: regenerateTaras Madan2026-01-201-35/+87
|
* dashboard/config: regenerate Linux configsAleksandr Nogikh2026-01-151-7/+17
| | | | | 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-69/+94
| | | | Use v6.18-rc1 and the latest linux-next tag.
* dashboard/config/linux: regenerate filesTaras Madan2025-10-061-89/+240
|
* dashboard/config/linux: disable CONFIG_CGROUP_BPFAleksandr Nogikh2025-07-171-3/+2
| | | | | | | | | | 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-73/+98
| | | | Use v6.16-rc1 and the latest linux-next tag.
* dashboard/config/linux: add upstream-rust-kasan configAleksandr Nogikh2025-05-201-2/+5
| | | | Enable RUST as well as other Rust-related configs.
* dashboard/config: enable ANDROID_BINDERFSAleksandr Nogikh2025-04-291-1/+1
| | | | 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-61/+115
| | | | Use the latest linux-next and torvalds releases.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2025-03-291-43/+82
| | | | 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: 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-65/+180
| | | | | 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/config/linux: regenerate configsDmitry Vyukov2024-08-301-25/+27
| | | | Regenerate deterministic configs.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2024-08-291-55/+96
| | | | | Regenerate the configs using the latest mainline, linux-next and stable versions.
* dashboard/config: regenerate configsAndrey Konovalov2024-07-251-107/+172
| | | | To enable new USB drivers from the distro configs added in the last patch.
* dashboard/config/linux: regenerate configsAleksandr Nogikh2024-06-181-21/+58
| | | | | Regenerate the configs using the latest RC and the latest linux-next tag.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2024-04-081-58/+391
| | | | | | Regenerate configs using latest Linux release candidate and linux-next. Enable more bcachefs configs.
* dashboard/configs: update linux configsAleksandr Nogikh2024-01-301-75/+184
| | | | Regenerate the configs using the latest Linux revisions.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2023-10-231-148/+172
| | | | | | | | | 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-2/+1
| | | | | | 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: regenerate Linux configsAleksandr Nogikh2023-07-131-5/+20
| | | | | 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: disable XFS_SUPPORT_V4Aleksandr Nogikh2023-07-031-1/+1
| | | | Closes #3918.
* dashboard/config/linux: update to latest upstreamMarco Elver2023-06-301-50/+53
| | | | | | | | | | | | | 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: enable CONFIG_ZSWAP_DEFAULT_ONAleksandr Nogikh2023-06-151-1/+1
|
* dashboard/config/linux: enable IOMMU/DMA configsDmitry Vyukov2023-04-271-5/+8
| | | | It seems we can cover them in qemu.
* dashboard/config/linux: update configs to latest kernelsDmitry Vyukov2023-04-271-29/+34
|
* dashboard/config/linux: update to latest kernelsDmitry Vyukov2023-04-031-53/+72
|
* dashboard/config/linux: enable DWARF4 for allDmitry Vyukov2023-02-181-2/+2
|
* dashboard/config/linux: enable LRU_GEN on some instancesDmitry Vyukov2023-02-151-1/+3
| | | | | As requested here: https://lore.kernel.org/linux-mm/20230215015231.3646-1-hdanton@sina.com/
* dashboard/config/linux: update to latest kernelDmitry Vyukov2023-02-151-2/+3
|
* dashboard/config/linux: update configsAleksandr Nogikh2023-01-261-33/+81
| | | | | | | 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 CONFIG_UFS_FS_WRITEDmitry Vyukov2022-11-281-1/+1
| | | | | | Enable write support for UFS. The description says experimental/dangerous, but seems to mean only that images can be corrupted ("you should back up your UFS partitions beforehand").
* dashboard/config/linux: disable CONFIG_XFS_DEBUGMarco Elver2022-11-221-2/+2
| | | | | Intended for XFS developers only: https://lkml.kernel.org/r/20221122043504.GR3600936@dread.disaster.area
* dashboard/config/linux: enable new configsDmitry Vyukov2022-11-141-7/+53
| | | | | Enable some new configs that are reachable in VMs and some new debugging configs.
* dashboard/config/linux: update upstream configsDmitry Vyukov2022-11-141-266/+489
| | | | | | | | | | | | | | | | | | | | | 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 `CONFIG_BTRFS_FS_REF_VERIFY`Hrutvik Kanabar2022-09-131-1/+1
| | | | | | | | This enables the `btrfs` extent references verification tool, introduced in torvalds/linux@fd708b81d972a0714b02a60eb4792fdbf15868c4. This instruments updates to extent references to verify their integrity. Hydra (https://taesoo.kim/pubs/2019/kim:hydra.pdf) uses this to discover several semantic bugs in `btrfs` code.
* 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-8/+9
| | | | 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
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-11 19:58:19 +0000