aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/chromeos-5.15-base.config
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config: regenerate Linux configsAleksandr Nogikh2026-01-151-4/+4
| | | | | No extra changes, just a newer Docker container to minimize noise in the following commits.
* dashboard/config/linux: regenerate filesTaras Madan2025-10-061-1/+1
|
* dashboard/config/linux: always enable GVNICAleksandr Nogikh2025-08-081-1/+1
|
* dashboard/config/linux: disable CONFIG_CGROUP_BPFAleksandr Nogikh2025-07-171-4/+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/linux: add upstream-rust-kasan configAleksandr Nogikh2025-05-201-4/+4
| | | | 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/configs: regenerate Linux configsAleksandr Nogikh2025-04-251-5/+7
| | | | Use the latest linux-next and torvalds releases.
* dashboard/config: regenerate clang configs with LLVM=1Aleksandr Nogikh2025-04-171-4/+3
|
* dashboard/config/linux: increase number of devices to 32Dmitry Vyukov2024-10-241-1/+1
|
* dashboard/config/linux: bump lockdep consts even moreDmitry Vyukov2024-08-301-2/+2
| | | | | Btrfs needs higher values to avoid false positives: https://lore.kernel.org/all/20240821201338.GA2109582@perftesting/
* dashboard/config: disable CONFIG_FRAME_WARN on ChromeOSAleksandr Nogikh2024-05-071-1/+1
| | | | As suggested by @groeck.
* dashboard/config: update ChromeOS configsAleksandr Nogikh2024-05-031-59/+126
| | | | | | | 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 Nogikh2023-07-131-5/+17
| | | | | 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: make Linux baseline configs smallerAleksandr Nogikh2023-07-041-1220/+14
| | | | Disable more kernel configs for baseline files.
* dashboard/config/linux: enable DWARF4 for allDmitry Vyukov2023-02-181-2/+2
|
* dashboard/config/linux: update ChromeOS 5.15 configsDmitry Vyukov2023-02-181-73/+188
|
* dashboard/config/linux: update configsAleksandr Nogikh2023-01-261-1/+1
| | | | | | | 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-1/+42
| | | | | Enable some new configs that are reachable in VMs and some new debugging configs.
* dashboard/config/linux: update upstream configsDmitry Vyukov2022-11-141-1/+0
| | | | | | | | | | | | | | | | | | | | | 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.
* 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
* dashboard/config/linux: enable CSD_LOCK_WAIT_DEBUGDmitry Vyukov2022-04-201-1/+1
| | | | | | As asked by Hillf here: https://lore.kernel.org/all/20220419134616.GE4285@paulmck-ThinkPad-P17-Gen-1/ This config can provide more precise diagnostic for some bugs.
* dashboard/config/linux: set CONFIG_WERROR=nMarco Elver2022-04-061-1/+1
| | | | | | | | | | | | | | | | | Our Clang+KASAN instance is breaking due to CONFIG_WERROR being turned on in x86_64 defconfig [1], which in turn is used to generate our baseline configs, and therefore has accidentally been enabled in our syzbot configs as well. This issue has been discussed in great detail when CONFIG_WERROR was first introduced, with the conclusion that it is the wrong default for runtime-test focused bots [2]. Therefore, disable CONFIG_WERROR for syzbot, to not have the odd compiler warning interrupt precious fuzzing time. [1] https://lore.kernel.org/all/000000000000008dae05dbfebd85@google.com/ [2] https://git.kernel.org/torvalds/c/b339ec9c229aaf399296
* dashboard/config: update configs to next-20220222Aleksandr Nogikh2022-02-241-1/+3
| | | | | | | | | Move CONFIG_AID_FOR_SYZBOT to verbatim since it has for some reason disappeared from the linux-next tree. Add CONFIG_RCU_EXP_CPU_STALL_TIMEOUT and set it to the maximum value. Otherwise it overwhelms syzbot with `INFO: rcu_preempt detected expedited stalls on CPUs/tasks` crashes.
* dashboard/config/linux: update ChromeOS configs to latest kernelsDmitry Vyukov2022-02-031-6/+10
| | | | Update configs to latest HEADs of chromeos-5.* branches.
* dashboard/config/linux: update upstream configsDmitry Vyukov2022-01-271-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: add ChromeOS 5.15 support (#2948)Taras Madan2021-12-291-0/+7439
To add the ChromeOS 5.15 configs. It required to disable the INCREMENTAL_FS support.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-11 20:15:34 +0000