aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/linux/bits
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config: enable SECURITY_SELINUX_DEVELOPAleksandr Nogikh2022-04-061-0/+1
| | | | | This option enables the "enforcing=?" option (at least), which simplifies SELINUX configuration.
* dashboard/config/linux: update linux configs to v5.18-rc1Taras Madan2022-04-066-9/+19
| | | | | update linux to v5.18-rc1 fix dependency update errors update configs
* dashboard/config/linux: disable KASAN_INLINE for riscv64Aleksandr Nogikh2022-03-081-1/+2
| | | | | | | | | Problems with KASAN_OUTLINE and some other instrumentations were recentely fixed in a series by Alexandre Ghiti. Fixes for KASAN_INLINE are also on the way. Switch syzbot's riscv instance to KASAN_OUTLINE to make it work after a 130+ day break.
* dashboard/config/linux: enable CONFIG_BACKTRACE_VERBOSE for armDmitry Vyukov2022-03-051-0/+2
| | | | | | | W/o this config arm stack traces don't include PC which we expect when parsing stack traces. It was added in May 13 2021, and it seems since then we classified all arm reports as corrupted.
* dashboard/config/linux: disable IO_URING for android 5.10Dmitry Vyukov2022-03-051-0/+20
|
* dashboard/config: update configs to next-20220222Aleksandr Nogikh2022-02-242-5/+10
| | | | | | | | | 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: enable TRANSPARENT_HUGEPAGE_MADVISEDmitry Vyukov2022-02-171-0/+1
| | | | | | This functionality is perfectly reachable for us via madvise. Reported-by: Brad Spengler
* dashboard/config/linux: enable KVM configs for ChromeOSDmitry Vyukov2022-02-031-0/+18
| | | | These are now enabled on real devices.
* dashboard/config/linux: update ChromeOS configs to latest kernelsDmitry Vyukov2022-02-033-3/+6
| | | | Update configs to latest HEADs of chromeos-5.* branches.
* dashboard/config/linux: disable deprecated FB configsDmitry Vyukov2022-01-312-7/+11
| | | | | Update FD/DRM configs based on Daniel recommendations here: https://lore.kernel.org/all/YfJ9yWW+MH8N4r4A@phenom.ffwll.local/
* dashboard/config/linux: enable ANON_VMA_NAME and DAMON_RECLAIMDmitry Vyukov2022-01-271-0/+2
| | | | Enable new configs in v5.17 that look interesting to us.
* dashboard/config/linux: update upstream configsDmitry Vyukov2022-01-2710-23/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: add arm/arm64 full configsDmitry Vyukov2022-01-131-6/+0
| | | | | | We generate slightly reduces configs for arm/arm64 b/c we test in slow qemu VMs. Add full versions of these configs that can be used with syz-check to avoid no-such-struct warnings.
* dashboard/config: add ChromeOS 5.15 support (#2948)Taras Madan2021-12-292-1/+11
| | | | To add the ChromeOS 5.15 configs. It required to disable the INCREMENTAL_FS support.
* dashboard/config: enable DRM_I915 in ChromeOS 5.10 (#2950)Taras Madan2021-12-291-5/+0
|
* dashboard/config: add chromeos-5.10 support (#2947)Taras Madan2021-12-271-0/+15
| | | To add the ChromeOS 5.10 support.
* dashboard/config: fix sybsystems.yml, DAMON supportTaras Madan2021-12-271-3/+3
|
* sys/linux: add Damon descriptionshatoboar2021-12-201-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | * sys/linux/damon.txt: initial description description of DAMON's interface mounted in debugfs: target_ids, attrs, init_regions, monitor_on * sys/linux/damon.txt: additional damon interface description added added DAMON interface descriptions for schemes, kdamond_pid, mk_contexts, rm_contexts prefix of all the files with damon to avoid colliding naming * sys/linux/damon.txt: standard copyright statement added * sys/linux/damon.txt.const: const file of sys/linux/damon.txt added * sys/linux/damon.txt: type fix of pid to fmt * dashboard/config/linux/bits/subsystems.yml: damon configs added for Syzbot * dashboard/config/linux: generated kernel configs with added damon config * sys/linux/damon.txt: fmt type fix * sys/linux/damon.txt: read and close syscalls removed write and read mk_contexts summarized into one syscall some refining of syscall interfaces
* dashboard/config/linux: reduce tomoyo learning quotaDmitry Vyukov2021-12-141-1/+2
| | | | | | | High values of CONFIG_SECURITY_TOMOYO_MAX_ACCEPT_ENTRY cause significant slowdown (see issue #2892). Reduce the value. Fixes #2892
* 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: update android 5.10 config (#2899)Taras Madan2021-12-011-1/+1
| | | | Updated the Android 5.10 base to 8d21bcc704ea1 (latest 5.10lts commit). Regenerated configs.
* kmsan: change panic_on_kmsan=1 to kmsan.panic=1Alexander Potapenko2021-11-191-1/+1
| | | | | | This is how the boot-time parameter is called now. Signed-off-by: Alexander Potapenko <glider@google.com>
* dashboard/config/linux: refactor lockdep configs into lockdep.ymlMarco Elver2021-11-092-17/+21
| | | | | | 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: enable networking subsystems for KCSAN instanceMarco Elver2021-11-091-1/+1
| | | | | | | Add the 'onlynet' tag and use it on the KCSAN instance. Strictly speaking 'wireless', 'bluetooth', and 'hamradio' could also be included in 'onlynet', but leave them out for now.
* dashboard/config/linux: refactor networking configs into net.ymlMarco Elver2021-11-093-514/+522
| | | | | Move most networking related configs to net.yml, including net drivers that are dependencies for various features.
* dashboard/config/linux: rename subsystems_net to net-extraMarco Elver2021-11-091-0/+0
|
* dashboard/config/linux: update configs to 5.15Marco Elver2021-11-094-4/+4
| | | | | | | 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-293-6/+7
| | | | | | 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-1/+1
| | | | | | | | | | | 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: disable CONFIG_KVM_WERROR for android-5.10 and ↵Taras Madan2021-10-211-0/+2
| | | | regenerate configs
* dashboard/config/linux: add secretmem_enable to cmdlineDmitry Vyukov2021-10-211-1/+2
| | | | | | | 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: preserve behavour exhibited by gki_defconfig buildLee Jones2021-10-201-0/+2
| | | | | | | "cgroup_disable=pressure cgroup.memory=nokmem" would affect kernel behaviour. Suggested-by: Dmitry Vyukov <dvyukov@google.com> Signed-off-by: Lee Jones <lee.jones@linaro.org>
* dashboard/config/linux: add support for Android v5.10Lee Jones2021-10-201-0/+13
| | | | | | | | | | | | 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>
* dashboard/config/linux: support back-ported KASAN_STACK{_ENABLE} rename in ↵Lee Jones2021-10-201-0/+3
| | | | | | | | | | | | Android KASAN_STACK_ENABLE was renamed to KASAN_STACK in kernel version v5.11. This change was also back-ported to android12-5.10, so we need to provide support for that here too or else `make configs` will complain that KASAN_STACK_ENABLE is not enabled. Signed-off-by: Lee Jones <lee.jones@linaro.org>
* dashboard/config/linux: kcsan: do not pretend writes are atomicMarco Elver2021-10-201-1/+1
| | | | | | | | | | | | | | | | Do not pretend writes are atomic. While this may currently be a prevailing preference in the community, it does hide more interesting bugs [1]. Since we moderate data races anyway, and are still drowning in data races, a few more won't hurt. What it does help with, however, is getting better signals about harmful data races. Most of the read/write data races provide weak signals, but write/write data races should provide a stronger harmfulness signal [1], which will help us in selecting data races to investigate further. [1] https://googleprojectzero.blogspot.com/2021/10/how-simple-linux-kernel-memory.html
* dashboard/config/linux: kcsan: remove KCSAN_DEBUGMarco Elver2021-10-201-1/+0
| | | | | CONFIG_KCSAN_DEBUG no longer exists, remove it. Older kernels will set it to 'n' by default.
* dashboard/config/linux: enable SCHED_COREDmitry Vyukov2021-10-131-0/+1
|
* dashboard/config/linux: update to lateest kernelsDmitry Vyukov2021-10-135-7/+7
| | | | | | Update to latest upstream, linux-next and kmsan. KMSAN stopped supporting few configs which depend on crypto and heap auto-init.
* dashboard/config/linux: update upstream and -nextMarco Elver2021-09-082-2/+2
| | | | | | Update the tags for upstream and -next and update all configs. This pulls in the CONFIG_WERROR disabled-by-default change.
* Revert "dashboard/config/linux: add nowerror.yml config fragment"Marco Elver2021-09-081-5/+0
| | | | | | This reverts commit 23e41b77c691a7e95d822c53f895f8d53326c342. The config fragment is now unused, remove it.
* dashboard/config/linux: update upstream and -nextMarco Elver2021-09-072-2/+2
| | | | Update the tags for upstream and -next and update all configs.
* dashboard/config/linux: mark configs removed from 5.14Marco Elver2021-09-073-3/+3
| | | | | | RAW_DRIVER: https://git.kernel.org/torvalds/c/603e4922f1c81fc2ed3a87b4f91a8d3aafc7e093 CAIF_HSI: https://git.kernel.org/torvalds/c/ca75bcf0a83b6cc7f53a593d98ec7121c4839b43 WWAN_CORE: https://git.kernel.org/torvalds/c/89212e160b81e778f829b89743570665810e3b13
* dashboard/config/linux: config DRM_FBDEV_EMULATION is required by ↵Marco Elver2021-09-071-0/+1
| | | | | | | | | DRM_VMWGFX_FBCON As of [1] DRM_VMWGFX_FBCON depends on DRM_FBDEV_EMULATION. It doesn't hurt to always enable it also on older kernels. [1] https://git.kernel.org/torvalds/c/5dbf2fc587cb79cb366bd6e79ac6b52269d64fc5
* dashboard/config/linux: config GVE has become LE onlyMarco Elver2021-09-071-1/+1
| | | | https://git.kernel.org/torvalds/c/223198183ff1fc099184081f997bf1f710f1ef72
* dashbaord/config/linux: config IDLE_PAGE_TRACKING will be brokenMarco Elver2021-09-071-1/+1
| | | | https://lkml.kernel.org/r/20210612000714.775825-1-willy@infradead.org
* dashboard/config/linux: config CIFS_WEAK_PW_HASH has been removedMarco Elver2021-09-071-1/+1
| | | | https://git.kernel.org/torvalds/c/76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c
* dashboard/config/linux: disable FORITFY_SOURCE for clangMarco Elver2021-09-071-1/+1
| | | | | Apparently it's broken with clang: https://lore.kernel.org/lkml/CAKwvOd=A+ueGV2ihdy5GtgR2fQbcXjjAtVxv3=cPjffpebZB7A@mail.gmail.com
* dashboard/config/linux: add nowerror.yml config fragmentMarco Elver2021-09-071-0/+5
| | | | | | | | Linux 5.15 will introduce -Werror to be on by default: https://git.kernel.org/torvalds/c/3fe617ccafd6f5bb33c2391d6f4eeb41c1fd0151 Introduce nowerror.yml that can be used for configs that are likely to be perpetually broken due to Werror.
* dashboard/config: kcsan: select CONFIG_KCSAN_PERMISSIVEMarco Elver2021-09-061-0/+1
| | | | | | | | | | | | The new CONFIG_KCSAN_PERMISSIVE is now supported in mainline: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa829778b16f15266fefe2640f04931b16ce39c0 Select it in the default syzbot config. The configs were updated manually, because we should wait until v5.15-rc1 is out (mainline is still in the merge window), at which point we can update upstream's commit hash for syz-kconf and regenerate all configs.
* dashboard/config/linux: increase printk buffer sizeDmitry Vyukov2021-07-061-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | There is a number of one-off "BUG: stack guard page was hit" bugs: https://syzkaller.appspot.com/bug?extid=b9419ddbdb57ce0e7f36 https://syzkaller.appspot.com/bug?extid=1ea34900b9a6fb8526c4 https://syzkaller.appspot.com/bug?extid=cd2009ad04934b665765 https://syzkaller.appspot.com/bug?extid=4e1ccdc40f48e600d960 Most likely these have the same root cause (recursion via call_netdevice_notifiers), and we should attribute them to one of top frames as we do for stalls. But we can't do this because in all these cases the stack is truncated and ends with: Lost 408 message(s)! Lost 394 message(s)! Lost 519 message(s)! These messages come from kernel/printk/printk_safe.c and happen when a "safe" buffer overflows. Increasing CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT should help to get complete parsable stack traces. The default value is 13 (8K). The largest number of lost lines I found is 519 and the longest line in the stack trace is 67 bytes. So that's 67*519+8K = 42965. Increase the config to 16 (64K). There are 2 such buffers per CPU (safe and nmi), so this will increase memory consumption to 128K per CPU. Should be fine.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-22 18:11:16 +0000