aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config
Commit message (Collapse)AuthorAgeFilesLines
...
* dashboard/config/linux: regenerate configsDmitry Vyukov2024-08-3032-543/+550
| | | | Regenerate deterministic configs.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2024-08-2961-1828/+3431
| | | | | Regenerate the configs using the latest mainline, linux-next and stable versions.
* dashboard/config: regenerate configsAndrey Konovalov2024-07-2531-2064/+3582
| | | | To enable new USB drivers from the distro configs added in the last patch.
* dashboard/configs: add Ubuntu 24.04 and Pixel 8 distro configsAndrey Konovalov2024-07-252-0/+19761
|
* dashboard/config: drop security modules bits from usb instanceAndrey Konovalov2024-07-232-95/+26
| | | | | | | | | | | | | | | | | | | | | CONFIG_SECURITY_TOMOYO produces a large amount of coverage entries for each ioctl call. For normal instances, this might not be a problem, as they call only a single ioctl for each syzkaller syscall. However, the syz_usb_connect pseudo-syscall calls a large number of ioctls. As a result, the KCOV coverage buffer for this syscall might overflow due to the tomoyo-produced entries. For example, with tomoyo, the first syscall of the vusb_ath9k runtest produces ~140k KCOV entries (with [1] applied), which is not far from the current 256k limit of KCOV entries per syscall. With tomoyo disabled, the number of entries falls to ~30k. Drop the security modules–related bits from the USB instance: I don't think they are useful for that instance anyway. [1] https://lore.kernel.org/all/eaf54b8634970b73552dcd38bf9be6ef55238c10.1718092070.git.dvyukov@google.com/
* dashboard/config: add -next configs for KMSANAlexander Potapenko2024-07-186-13/+14457
| | | | | | | | 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.
* dashboard/config: enable LRU_GEN for most instancesDmitry Vyukov2024-07-1021-27/+78
| | | | | It's not the default for most kernels, so it makes sense to test it more. E.g. for KCSAN, KMSAN we have only 1 instance, makes sense to test LRU_GEN.
* dashboard/config/linux: regenerate configsAleksandr Nogikh2024-06-1839-759/+1901
| | | | | Regenerate the configs using the latest RC and the latest linux-next tag.
* dashboard/config: add upstream-arm64-kasan_sw-kcov.configAlexander Potapenko2024-06-115-1/+13918
| | | | | The new config will enable KASAN_SW_TAGS and KCOV. Also make sure KVM_SW_PROTECTED_VM is only enabled on x86_64.
* dashboard/config: disable CONFIG_FRAME_WARN on ChromeOSAleksandr Nogikh2024-05-079-8/+10
| | | | As suggested by @groeck.
* dashboard/config: update ChromeOS configsAleksandr Nogikh2024-05-0316-545/+16126
| | | | | | | 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.
* all: remove akaros supportDmitry Vyukov2024-04-151-87/+0
| | | | | | | Akaros support is unused, it was shutdown on syzbot for a while, the akaros development seems to be frozen for years as well. We have a bunch of hacks for Akaros since it supported only super old gcc and haven't supported Go. Remove it.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2024-04-0839-1346/+4600
| | | | | | Regenerate configs using latest Linux release candidate and linux-next. Enable more bcachefs configs.
* dashboard/config: temporarily disable CONFIG_DEBUG_LIST for KMSANAlexander Potapenko2024-02-153-3/+4
| | | | | | | KMSAN is currently reporting boot-time false positives in debugging code called from stackdepot.c (see https://github.com/google/syzkaller/issues/4504) Disable CONFIG_DEBUG_LIST under KMSAN until the fix lands.
* dashboard/config: use clang for upstream-apparmor-kasan.configAleksandr Nogikh2024-02-013-39/+31
|
* dashboard/configs: update linux configsAleksandr Nogikh2024-01-3061-2239/+6633
| | | | Regenerate the configs using the latest Linux revisions.
* dashboard: disable CONFIG_BLK_DEV_WRITE_MOUNTEDAleksandr Nogikh2023-11-1313-222/+310
| | | | | | | This has become possible with the new series from Jan Kara: https://lore.kernel.org/all/20231101173542.23597-1-jack@suse.cz/ Regenerate configs on the latest linux-next.
* dashboard/config: updated android14-5.15 config tagLiz Prucka2023-10-312-12/+45
| | | | | Commit 4553bf0cfac5 added CONFIG_BLK_DEV_NULL_BLK as required to the gki_defconfig. Updated the android14-5.15 config to build off the most recent commit to reflect this.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2023-10-2337-2731/+5193
| | | | | | | | | 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: update unmaintained.ymlAleksandr Nogikh2023-10-231-1/+1
| | | | Reorder configs in a proper way.
* dashboard/config: add config with unmaintained partsAleksandr Nogikh2023-10-1916-26/+10320
| | | | | | Disable unmaintained code parts (at least those known so far) in existing configs and enable them in a special upstream-unmaintained.config file.
* dashboard: make qemu arm64 configs compile againAleksandr Nogikh2023-08-103-6/+6
| | | | | | | | | | | | | | 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: move OpenBSD to us-central1-bAleksandr Nogikh2023-08-081-1/+1
| | | | Let's spread the load more evenly.
* dashboard: enable CONFIG_PVH from v5.0Aleksandr Nogikh2023-08-071-1/+1
| | | | It's not present in earlier versions.
* dashboard/config: switch KMSAN configs to upstream treeAlexander Potapenko2023-08-024-19/+11
| | | | | Since we are using the upstream tree to build KMSAN on syzbot, switch the kernel configs to also reference that tree.
* dashboard/config: regenerate Linux configsAleksandr Nogikh2023-07-1374-383/+19406
| | | | | 1) Migration to a new Docker image changed toolchain versions. 2) Regenerate cuttlefish configs that were previously omitted.
* dashboard/config: generate Linux 5.10 LTS configsAleksandr Nogikh2023-07-078-2/+31707
|
* dashboard/config: enable virtualization configs for KMSANAleksandr Nogikh2023-07-054-5/+44
| | | | This also lets us enable CONFIG_PVH for it.
* dashboard/config: enable CONFIG_PVH for Linux/x86_64Aleksandr Nogikh2023-07-0537-36/+39
| | | | This will let users boot directly from the vmlinux file.
* dashboard/config: make Linux baseline configs smallerAleksandr Nogikh2023-07-0434-20789/+465
| | | | Disable more kernel configs for baseline files.
* tools/syz-kconf: split the `baseline` featureAleksandr Nogikh2023-07-047-16/+16978
| | | | | | | | | | | | | | | | Baseline configs were meant to be the minimum configs, however, since they are based on defconfigs, they are still quite big. To facilitate even smaller baseline configs, let's split the `baseline` feature in two: 1) `baseline` only disables the addition of extra features on top of baseline config. It's enabled for `-base.config` files automatically, but can be also manually set, e.g. if we only want to add debug configs on top of a defconfig. 2) `base-config` is automatically set for `-base.config` files and can be used to disable configs in those files. Regenerate configs.
* dashboard/config: disable XFS_SUPPORT_V4Aleksandr Nogikh2023-07-0313-13/+18
| | | | Closes #3918.
* dashboard/config/linux: update to latest upstreamMarco Elver2023-06-3032-994/+1576
| | | | | | | | | | | | | 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/linux: introduce upstream-kasan-badwrites.configMarco Elver2023-06-304-0/+14793
| | | | | | | | | | | | | | | | | Introduce a variant of upstream-apparmor-kasan, which enables: - kasan.fault=panic_on_write [1] - kasan_multi_shot, so that panic_on_warn does cause KASAN to panic on bad non-write accesses As discussed in [1], "KASAN reported invalid _writes_ are of special interest, because they have greater potential to corrupt random kernel memory or be more easily exploited." With this config we can set up a syzbot instance that can detect such issues. [1] https://lore.kernel.org/linux-mm/20230614095158.1133673-1-elver@google.com/
* dashboard/config, tools/syz-kconf: add Cuttlefish supportLiz Prucka2023-06-298-5/+20732
| | | | | | | Allow modules in config if `modules` are specified in main.yml. Added Cuttlefish instances for android13-5.10, android13-5.15, and android14-5.15 branches.
* dashboard/config/linux: bump Android kernels and configsTudor Ambarus2023-06-2912-155/+96
| | | | | | | 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>
* dashboard/config: enable EXT4_FS_SECURITY for SELinuxAleksandr Nogikh2023-06-286-5/+7
|
* dashboard/config/linux/README.md: fix typoTaras Madan2023-06-261-1/+1
|
* dashboard/config: enable CONFIG_ZSWAP_DEFAULT_ONAleksandr Nogikh2023-06-1517-16/+17
|
* dashboard: add ChromeOS 6.1 configs (#3932)Aleksandr Nogikh2023-06-015-1/+15976
|
* dashboard: add COS-6.1 configsAleksandr Nogikh2023-05-304-0/+8688
|
* dashboard/config/linux: disable CONFIG_STACKPROTECTOR for KMSANAlexander Potapenko2023-05-093-204/+239
| | | | | | | | | | | | | | | | | | | | | | | | | | Linux v6.4-rc1 built with Clang versions <= 16 with stack protector enabled panic with the following stack trace: Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: start_kernel+0xd8a/0xd90 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.3.0-rc1-00042-g9ea7e6b62c2b-dirty #106 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 dump_stack_lvl+0x1bc/0x250 lib/dump_stack.c:106 dump_stack+0x1e/0x20 lib/dump_stack.c:113 panic+0x4cd/0xc10 kernel/panic.c:340 __stack_chk_fail+0x18/0x20 kernel/panic.c:759 start_kernel+0xd8a/0xd90 init/main.c:? x86_64_start_reservations+0x2e/0x30 arch/x86/kernel/head64.c:556 x86_64_start_kernel+0x118/0x120 arch/x86/kernel/head64.c:537 secondary_startup_64_no_verify+0xcf/0xdb arch/x86/kernel/head_64.S:358 </TASK> https://github.com/ClangBuiltLinux/linux/issues/1815 describes the problem, which is fixed on the Clang side (https://reviews.llvm.org/D147975), but before the fix reaches syzbot we'll have to keep the stack protector disabled.
* dashboard/config/linux: add support for Android 6.1Tudor Ambarus2023-05-044-0/+15511
| | | | | | | Add support for Android 6.1. The configs are for 'android14-6.1', there's no android-6.1-lts available yet. Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
* Revert "dashboard: bump CONFIG_FRAME_WARN for Android kernels"Tudor Ambarus2023-05-047-8/+6
| | | | | | | | | | | | | | | | 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: update to latest Android 5.15-ltsTudor Ambarus2023-05-043-65/+73
| | | | | | Update configs to latest android13-5.15-lts. Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
* dashboard/config/linux: change branch and update to latest Android 5.10-ltsTudor Ambarus2023-05-043-161/+312
| | | | | | | | | 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/config/linux: update to latest Android 5.4-ltsTudor Ambarus2023-05-044-158/+333
| | | | | | | Update configs to latest android12-5.4-lts. Get rid of CONFIG_REFCOUNT_FULL as the patch removing it got integrated. Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
* dashboard: enable CONFIG_PAGE_TABLE_CHECK for emu targetsSpace Meyer2023-05-025-6/+10
| | | | | | | | | | 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/openbsd: simpify image buildingGreg Steuck2023-04-281-1/+0
| | | | | The config is now reference directly from its original location. The old way was a carry-over from days long gone.
* dashboard: enable CONFIG_PAGE_TABLE_CHECK on Linux targetsAleksandr Nogikh2023-04-2815-14/+30
|
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-11 20:58:42 +0000