aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/config/upstream.sysctl
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/config: delete old configsDmitry Vyukov2020-10-211-19/+0
| | | | | | | | All configs were moved into per-OS dirs in "dashboard/config: move OS configs into separate dirs". The move is deployed on syzbot. Delete old configs. Update #2171
* dashboard/config: enable more things in linux configDmitry Vyukov2018-09-071-0/+2
| | | | Enable configs that are enabled in android/chromeos.
* dashboard/config: update kernel configsDmitry Vyukov2018-08-291-0/+1
| | | | | | | | | | | | | | | | - enable usbip - enable squashfs - enable ubifs - enable dm-verity - enable IMA/EVM /\/\/\ all things we want to test - set hung_task_check_interval_secs = 20 for more precise hung detection - switch to apparmor (we don't enable selinux anyway) - update to latest kernel Update #533
* dashboard/config: add fs.mount-max = 100 sysctlDmitry Vyukov2018-07-181-0/+10
| | | | | See "mnt: Add a per mount namespace limit on the number of mounts" commit for details.
* dashboard/config: tune kernel timeoutsDmitry Vyukov2018-07-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | See #516 for description of the problem. The new scheme is: 1. RCU stalls the highest priority. CONFIG_RCU_CPU_STALL_TIMEOUT=100 which results in stalls detected after 100-101 secs. 2. Then softlockup detector. kernel.watchdog_thresh = 55 (sysctl) which surprisingly detects stalls after 110-132 secs. 3. Then hung tasks and workqueue stalls. Unfortunately we can't separate them because that would require setting "no output" timeout to 10+ minutes. workqueue.watchdog_thresh=140 (cmdline) CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=140 Both are detected after 140-280 secs. 4. Finally, "no output" crashes. Detected by vm.MonitorExecution after 300 secs. Fixes #516
* bpf: disable hardening in favor of unwindingDaniel Borkmann2018-07-051-1/+1
| | | | | | | | | | | | | | | | | I had missed that once hardening is enabled, it automatically disables any exposure of JITed addresses, therefore when crashes or warnings are thrown we don't unwind beyond a helper function. For now disable hardening. After merge window I'll see if it's possible to detangle the case where kernel queries kallsyms internally to find function names whenever a WARN or BUG is thrown. If that's not possible easily, we can potentially add a harden mode 3 which does hardening but does not disable kallsyms exposure and then set this here for tools like syzkaller. Fixes: ac9b19d2e435 ("bpf: enable hardening mode 1 for jited images") Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> [dvyukov: also updated dashboard/config/upstream.sysctl]
* dashboard/config: add syzbot configsDmitry Vyukov2018-06-111-0/+6