aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/instance/instance_test.go
diff options
context:
space:
mode:
authorMarco Elver <elver@google.com>2023-06-29 14:21:27 +0200
committerMarco Elver <elver@google.com>2023-06-30 15:06:06 +0000
commit77fea9231d86fc49b057fc23851653f880d6db0f (patch)
treece18ef102a851ef6639f76ba92239f1e53bcce65 /pkg/instance/instance_test.go
parent01298212bf09f73286ff351db3853e1137147a60 (diff)
dashboard/config/linux: introduce upstream-kasan-badwrites.config
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/
Diffstat (limited to 'pkg/instance/instance_test.go')
0 files changed, 0 insertions, 0 deletions