aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/bits/debug.yml
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config/linux: enable more configsTaras Madan2026-01-201-0/+2
| | | | | | 1. DEBUG_GENERIC_PT. 2. DEBUG_XARRAY. 3. PHY_GOOGLE_USB.
* dashboard/config/linux/bits: enable DEBUG_BUGVERBOSE_DETAILEDTaras Madan2026-01-201-0/+1
| | | | Closes #6595.
* dashboard/config/linux: update to v6.19-rc5Taras Madan2026-01-201-1/+0
|
* dashboard: regenerate Linux configsPimyn Girgis2025-10-201-0/+1
| | | | Use v6.18-rc1 and the latest linux-next tag.
* dashboard/config: add stable-6.6 configsAleksandr Nogikh2025-06-161-1/+1
|
* dashboard/config/linux: update to v6.13 and latest nextAleksandr Nogikh2025-01-301-1/+1
| | | | | Remove the deprecated options. Replace old "linux-next" conditions with the version numbers.
* dashboard/config: update ChromeOS configsAleksandr Nogikh2024-05-031-1/+1
| | | | | | | 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/configs: update linux configsAleksandr Nogikh2024-01-301-1/+1
| | | | Regenerate the configs using the latest Linux revisions.
* dashboard: enable CONFIG_PAGE_TABLE_CHECK for emu targetsSpace Meyer2023-05-021-2/+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: enable CONFIG_PAGE_TABLE_CHECK on Linux targetsAleksandr Nogikh2023-04-281-0/+2
|
* dashboard/config/linux: enable new configsDmitry Vyukov2022-11-141-0/+2
| | | | | Enable some new configs that are reachable in VMs and some new debugging configs.
* dashboard/config/linux: update upstream configsDmitry Vyukov2022-11-141-6/+3
| | | | | | | | | | | | | | | | | | | | | 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/linux: enable CSD_LOCK_WAIT_DEBUGDmitry Vyukov2022-04-201-0/+4
| | | | | | 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: update upstream configsDmitry Vyukov2022-01-271-9/+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/linux: enable REFCNT_TRACKER configsDmitry Vyukov2021-12-131-0/+9
| | | | | New debugging configs in net-next. Eric asks to enable them.
* dashboard/config/linux: refactor lockdep configs into lockdep.ymlMarco Elver2021-11-091-17/+0
| | | | | | All of lockdep comes with a number of config options, so let's refactor it into a separate lockdep.yml, which makes it easier to disable selectively.
* dashboard/config/linux: update to v5.13Dmitry Vyukov2021-05-121-5/+5
|
* dashboard/config/linux: bump LOCKDEP_STACK_TRACE_BITSDmitry Vyukov2021-04-201-1/+1
| | | | | | | | Once we've bumped other capacity values, "BUG: MAX_STACK_TRACE_ENTRIES too low!" started happening as well: https://syzkaller.appspot.com/bug?id=4ebb151b4e3ef885165669fea5b4cf1f2e353ab0 https://groups.google.com/g/syzkaller-upstream-moderation/c/8FK5kogGHM4 Bump LOCKDEP_STACK_TRACE_BITS by 1.
* dashboard/config/linux: support for v4.15 kernelsDmitry Vyukov2021-04-161-4/+5
| | | | | | | Add constraints for configs not present in v4.15. I tentatively marked all of them as v4.16. If we support something in between v4.15 and v5.4 in future we may need to refine them.
* dashboard/config/linux: tune LOCKDEP capacityDmitry Vyukov2021-04-141-1/+5
| | | | | | | | | | We are seeing the following warnings from LOCKDEP: BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! BUG: MAX_LOCKDEP_CHAINS too low! BUG: MAX_LOCKDEP_ENTRIES too low! Increase the corresponding capacity constants.
* dashboard/config/linux: enable CONTEXT_TRACKING_FORCEDmitry Vyukov2021-03-181-0/+4
|
* dashboard/config: enable DEBUG_TIMEKEEPING and FW_LOADERDmitry Vyukov2021-03-111-0/+1
| | | | | DEBUG_TIMEKEEPING enables some debug checks. FW_LOADER_USER_HELPER was enabled on arm/android but not on x86_64.
* dashboard/config/linux: enable new configsDmitry Vyukov2021-03-051-0/+1
| | | | Enable some new configs that look reachable in VMs.
* dashboard/config/linux: remove panic_on_warn from kcsan/kmsanDmitry Vyukov2021-03-031-0/+3
| | | | These instances ignore WARNINGs, so they don't want panic_on_warn.
* dashboard/config/linux: add arm configDmitry Vyukov2020-12-301-2/+2
|
* dashboard/config/linux: enable lockdep on arm64Dmitry Vyukov2020-12-291-13/+11
| | | | It seems to be working now.
* dashboard/config/linux: update to v5.11-rc11Dmitry Vyukov2020-12-291-4/+2
| | | | Also bump KMSAN to latest kmsan-v5.10-rc4.
* dashboard/config/linux: tune non-x86 timeoutsDmitry Vyukov2020-12-281-1/+0
| | | | | | Qemu emulation makes execution slower so we need to scale all hang/stall timeouts as well. Scale them by 3 to account for sys/targets.Timeouts.Scale which is set to 3.
* dashboard/config/linux: enable some new configsDmitry Vyukov2020-12-271-0/+4
| | | | Enable new things in v5.11 that we can reach.
* dashboard/config/linux: add s390 configDmitry Vyukov2020-12-271-7/+7
|
* dashboard/config/linux: add riscv64 configDmitry Vyukov2020-12-251-3/+3
|
* dashboard/config/linux: enable HW_RANDOM_VIRTIODmitry Vyukov2020-10-291-11/+14
| | | | | | | | HW_RANDOM_VIRTIO/RANDOM_TRUST_CPU/RANDOM_TRUST_BOOTLOADER help to initialize random pool faster. +mark some x86_64-specific configs as such in preparataion for arm64 support.
* dashboard/config/linux: resolve TODOsDmitry Vyukov2020-10-211-5/+3
| | | | | | | Resolve all TODOs that were left during the switch from old to new configs to minimize diffs. Update #2171
* dashboard/config/linux: add config fragmentsDmitry Vyukov2020-10-211-0/+57
Add config fragments for the new config generation system. Update #2171
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-12 02:14:05 +0000