Dmitry Vyukov

CONFIG_RANDOMIZE_BASE does not work for kernel modules since we subtract vmlinux's kaslr_offset() from modules as well, right? > - Always use KernelModule instead of ptr. Why do we need this?...

> > > CONFIG_RANDOMIZE_BASE does not work for kernel modules since we subtract vmlinux's kaslr_offset() from modules as well, right? > > > > > > There was a recent...

All gvisor instances started failing with: ``` failed to create rpc server: no symbol section ```

Sent https://github.com/google/syzkaller/pull/4974

How many bisections are there where a single failure kept it on the right path? Flakiness is a real thing as well, and we increase number of runs for flaky...

Perhaps there are now too many false "lost connection", "no output" and "SYZFAIL" now? Ideally these are kept under control. If there are too many of these, we can as...

This can make sense. There was some flag to mark unreliable bisections. We could mark them with the flag and not report.

Wonder if it's possible to call interrupt functions directly... or can we just JMP onto the function? If it's possible to call it, then we could add a nice boot...

More docs on virtio: http://docs.oasis-open.org/virtio/virtio/v1.0/cs04/virtio-v1.0-cs04.html#x1-360006 And some particularly interesting parts: http://docs.oasis-open.org/virtio/virtio/v1.0/cs04/virtio-v1.0-cs04.html#x1-90002 http://docs.oasis-open.org/virtio/virtio/v1.0/cs04/virtio-v1.0-cs04.html#x1-1570001 http://docs.oasis-open.org/virtio/virtio/v1.0/cs04/virtio-v1.0-cs04.html#x1-2020002

The ultimate goal for virtio fuzzing may be to make the fuzzer reach net/wifi/input stacks via connected virtio device, i.e. make the fuzzer pretend there is a new virtio net...