aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/android-5.10-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/config: set SERIAL_8250_RUNTIME_UARTS=4Aleksandr Nogikh2025-04-281-1/+1
| | | | | | | | | 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/configs: regenerate Linux configsAleksandr Nogikh2025-04-251-5/+5
| | | | 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: regenerate Linux configsAleksandr Nogikh2023-07-131-4/+4
| | | | | 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-650/+12
| | | | Disable more kernel configs for baseline files.
* dashboard/config/linux: bump Android kernels and configsTudor Ambarus2023-06-291-4/+4
| | | | | | | Bump the Android kernels to their latest SHAs and generate the kernel configs using tools/syz-env. Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
* Revert "dashboard: bump CONFIG_FRAME_WARN for Android kernels"Tudor Ambarus2023-05-041-1/+1
| | | | | | | | | | | | | | | | This reverts commit d341bdbd6837aa0214ee9dfd1c3ddfc58c2a0c9c. The bump of CONFIG_FRAME_WARN was done for Android 5.10 with the hope to get rid of the -Wframe-larger-than errors that were hit when KASAN_STACK && CC_IS_CLANG were set. Unfortunately this didn't fix the build as the stack instrumentation when using clang is broken and the errors were hit again as we can't predict the increase of the stack. The fix is to disable CONFIG_WERROR which now is done because we just bumped the Android 5.10 kernel config (which contains CONFIG_WERROR=y) and the kernel config tweak that disables CONFIG_WERROR now does its job (see dashboard/config/linux/bits/base.yml). Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
* dashboard/config/linux: change branch and update to latest Android 5.10-ltsTudor Ambarus2023-05-041-79/+148
| | | | | | | | | Change the Android 5.10-lts branch and update the configs to latest android13-5.10-lts (higher EOL). This also fixes the build error reported at link, as CONFIG_WERROR is now unset. Link: https://syzkaller.appspot.com/bug?id=0f1e1644d7ed28d1d925d6c9e2e2c0c1c18cb794 Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
* dashboard: bump CONFIG_FRAME_WARN for Android kernelsAleksandr Nogikh2023-04-191-1/+1
| | | | | We are not able to build Android 5.10 because of that warning for already more than 100 days. Just in case bump it for all Androids.
* dashboard/config: update linux configs with clang 15Aleksandr Nogikh2023-02-071-2/+2
|
* 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/+39
| | | | | 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: 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: regenerate configsAleksandr Nogikh2022-04-061-2/+2
| | | | | | Switch arm64 instances to clang. Enable KCOV for arm64. Regenerate configs with clang13.
* dashboard/config/linux: disable IO_URING for android 5.10Dmitry Vyukov2022-03-051-2/+1
|
* 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: update android 5.10 config (#2899)Taras Madan2021-12-011-6/+12
| | | | Updated the Android 5.10 base to 8d21bcc704ea1 (latest 5.10lts commit). Regenerated configs.
* dashboard/config/linux: run make configs under syz-envDmitry Vyukov2021-11-091-3/+3
| | | | | | make configs uses host compilers. This produces constant diffs in the generated configs related to different compiler versions. Suggest to run make configs under syz-env and check-in configs produced this way.
* dashboard/config/linux: update configs to 5.15Marco Elver2021-11-091-1/+1
| | | | | | | 5.15 was released, update a few TODOs that were dependent on 5.15 being properly released. Re-generate all configs.
* dashboard/config: enable binderfsAleksandr Nogikh2021-10-291-3/+3
| | | | | | Also, create only 2 binder devices at binderfs creation - we don't need 32 devices anymore, as a separate binderfs instance is now created per each syz-executor.
* dashboard/config/linux: fix secretmem parameter nameDmitry Vyukov2021-10-221-2/+2
| | | | | | | | | | | I think it's secretmem.enable rather than secretmem_enable. I can't find any useful docs. Here: module_param_named(enable, secretmem_enable, bool, 0400); What is the param name? If it's prefixed with module name, what's the module name for non-modules? What are the values for bool flags? Does no value at all enable it?
* dashboard/config/linux: add secretmem_enable to cmdlineDmitry Vyukov2021-10-211-205/+136
| | | | | | | secretmem_enable is required to enable memfd_secret syscall: https://elixir.bootlin.com/linux/v5.15-rc6/source/mm/secretmem.c#L202 (the android 5.10 base config was not generated on HEAD somehow)
* dashboard/config/linux: add support for Android v5.10Lee Jones2021-10-201-0/+6680
The tag that is provided is from 'android12-5.10-lts'. The LTS version must be used, as it is more up-to-date in terms of security fixes and stable back-ports than its non-lts counterpart. Using a tag from the non-lts branch will result in lots of false positives which would end up wasting quality engineering time. Signed-off-by: Lee Jones <lee.jones@linaro.org>
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-11 21:52:07 +0000