aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/upstream-arm64-kasan.config
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config/linux: regenerateTaras Madan2026-01-201-72/+97
|
* 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: enable ext4 in base configPimyn Girgis2025-10-221-1/+9
| | | | Ext4 is necessary for normal boot, enable it unconditionally in base.
* dashboard: regenerate Linux configsPimyn Girgis2025-10-211-15/+2
| | | | Disable rust by default for all instance, only enabling it where it's specified.
* dashboard: regenerate Linux configsPimyn Girgis2025-10-201-56/+96
| | | | Use v6.18-rc1 and the latest linux-next tag.
* dashboard/config/linux: regenerate filesTaras Madan2025-10-061-84/+280
|
* dashboard/config/linux: always enable GVNICAleksandr Nogikh2025-08-081-1/+1
|
* dashboard/config/linux: disable CONFIG_CGROUP_BPFAleksandr Nogikh2025-07-171-5/+5
| | | | | | | | | | 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: regenerate Linux configsAleksandr Nogikh2025-06-131-73/+101
| | | | Use v6.16-rc1 and the latest linux-next tag.
* dashboard/config/linux: add upstream-rust-kasan configAleksandr Nogikh2025-05-201-6/+10
| | | | Enable RUST as well as other Rust-related configs.
* dashboard/config: enable ANDROID_BINDERFSAleksandr Nogikh2025-04-291-5/+5
| | | | 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-51/+91
| | | | Use the latest linux-next and torvalds releases.
* dashboard/config: regenerate clang configs with LLVM=1Aleksandr Nogikh2025-04-171-3/+6
|
* dashboard/config: regenerate Linux configsAleksandr Nogikh2025-03-291-46/+83
| | | | 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-52/+215
| | | | | Remove the deprecated options. Replace old "linux-next" conditions with the version numbers.
* dashboard/config/linux: update configsTaras Madan2024-11-251-1/+6
| | | | 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: restore CMDLINE_FROM_BOOTLOADER on arm64Aleksandr Nogikh2024-09-131-3/+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-1/+1
| | | | | Btrfs needs higher values to avoid false positives: https://lore.kernel.org/all/20240821201338.GA2109582@perftesting/
* dashboard/config/linux: regenerate configsDmitry Vyukov2024-08-301-29/+27
| | | | Regenerate deterministic configs.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2024-08-291-91/+97
| | | | | Regenerate the configs using the latest mainline, linux-next and stable versions.
* dashboard/config: regenerate configsAndrey Konovalov2024-07-251-50/+65
| | | | To enable new USB drivers from the distro configs added in the last patch.
* dashboard/config/linux: regenerate configsAleksandr Nogikh2024-06-181-22/+66
| | | | | Regenerate the configs using the latest RC and the latest linux-next tag.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2024-04-081-60/+90
| | | | | | Regenerate configs using latest Linux release candidate and linux-next. Enable more bcachefs configs.
* dashboard/configs: update linux configsAleksandr Nogikh2024-01-301-81/+169
| | | | Regenerate the configs using the latest Linux revisions.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2023-10-231-78/+241
| | | | | | | | | 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: make qemu arm64 configs compile againAleksandr Nogikh2023-08-101-3/+2
| | | | | | | | | | | | | | We've been running into the following error: error: static declaration of 'mem_encrypt_init' follows non-static declaration The problem was caused by Kconfig not being able to adjust the depenencies, the fix is already coming: https://lore.kernel.org/lkml/CANp29Y6AnNeouWgAevBEDZcYcOjzDQwxLDfLxe41Lp3BC=h8bA@mail.gmail.com/T/ After it's merged, we'll have to update our configs anyway. So let's do it now.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2023-07-131-6/+5
| | | | | 1) Migration to a new Docker image changed toolchain versions. 2) Regenerate cuttlefish configs that were previously omitted.
* dashboard/config/linux: update to latest upstreamMarco Elver2023-06-301-41/+54
| | | | | | | | | | | | | 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 EXT4_FS_SECURITY for SELinuxAleksandr Nogikh2023-06-281-1/+1
|
* dashboard/config: enable CONFIG_ZSWAP_DEFAULT_ONAleksandr Nogikh2023-06-151-1/+1
|
* dashboard: enable CONFIG_PAGE_TABLE_CHECK for emu targetsSpace Meyer2023-05-021-1/+2
| | | | | | | | | | The way syz-kconf works, having the reference to timeouts_emu here means users must have at least one config using timeouts_emu, otherwise syz-kconf will complain. We don't use -timeouts_emu for any of our other common config patches. CONFIG_PAGE_TABLE_CHECK is not even one of our more expensive config patches. Let's not give it a special treatment.
* dashboard/config/linux: update configs to latest kernelsDmitry Vyukov2023-04-271-29/+44
|
* dashboard/config/linux: update to latest kernelsDmitry Vyukov2023-04-031-59/+83
|
* 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/+2
|
* dashboard/linux: switch clang configs to DWARF4Aleksandr Nogikh2023-02-081-2/+2
| | | | Currently syzbot is unable to symbolize reports for DWARF5.
* dashboard/config: update linux configs with clang 15Aleksandr Nogikh2023-02-071-3/+11
|
* dashboard/config/linux: update configsAleksandr Nogikh2023-01-261-42/+71
| | | | | | | 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 new configsDmitry Vyukov2022-11-141-6/+54
| | | | | Enable some new configs that are reachable in VMs and some new debugging configs.
* dashboard/config/linux: update upstream configsDmitry Vyukov2022-11-141-243/+452
| | | | | | | | | | | | | | | | | | | | | 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 debug options for the arm64-full configAleksandr Nogikh2022-08-051-1/+1
| | | | Also, factor emulation-dependent consts into a separate file.
* dashboard/config/linux: increase LOCKDEP size constsDmitry Vyukov2022-06-031-2/+2
| | | | | | | | We are still seeing some of: BUG: MAX_LOCKDEP_CHAINS too low! BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! BUG: MAX_LOCKDEP_ENTRIES too low! Bump LOCKDEP consts by 1.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-11 20:35:32 +0000