Dmitry Vyukov

I would assume it will be quite difficult to this since, since it a major architecture redesign. The advantages and disadvantages listed in the issue descirption.

Hard to say w/o doing it :) Will also depend a lot on who will do it (syzkaller/Go knowledge) and also on exact scope (remove all Go code from target,...

Precise detection of over-reads/over-writes is more the EFAULT part of #200. Even over-reads of what kernel is supposed to read are bad. Yes, we could detect these. I see this...

Related kernel KASAN feature request that may help to detect some user-space corruptions: https://bugzilla.kernel.org/show_bug.cgi?id=218153

FTR this may be a case of user-space corruption due to kernel bug in OpenBSD: https://syzkaller.appspot.com/bug?extid=0292611d290be27409bb https://groups.google.com/g/syzkaller-openbsd-bugs/c/tzNH3_Aa7fM/m/WVu1fvj_AwAJ ``` panic: time: Stop called on uninitialized Timer goroutine 8605 [running]: time.(*Timer).Stop(...) [/usr/local/go/src/time/sleep.go:79](https://github.com/openbsd/src/blob/7e284d508f03134ed914e01310f81a72255d0731//usr/local/go/src/time/sleep.go#L79)...

FTR another paper on automatic interface extraction: [KSG: Augmenting Kernel Fuzzing with System Call Specification Generation](https://www.usenix.org/conference/atc22/presentation/sun)

One interesting addition to this is analysis of what interfaces are reachable on with different privileges (non-privileged, requires userns, root-only). This info can also be crossed with coverage reports to...

cc @FlorentRevest

Other possible improvements for C reproducers: 1. Move test syscalls to the top of the reproducer (may require some forward declarations). The syscalls is the varying part, these are usually...

Maybe we could boot another VM with that disk to extract contents? Wonder if there is disk hot plug... then we could just attach it to the syz-manager machine. However,...