Dmitry Vyukov 559fbe2dbe syz-fuzzer: don't include disabled syscall name in panics ...

These checks still fire episodically [on gvisor instance only?].
I've done several attempts to debug this/extend checks.
But so far I have no glue and we are still seeing them.
They are rare enough to be directly debuggable and to be
something trivial. This may be some memory corruption
(kernel or our race), or some very episodic condition.
They are rare enough to be a problem, so don't include
syscall name so that they all go into a single bug bucket.

2020-06-16 16:10:59 +02:00

..

fuzzer_test.go

prog: support disabled attribute

2020-05-04 20:56:20 +02:00

fuzzer.go

all: use more respective language

2020-06-11 23:19:34 +02:00

proc.go

syz-fuzzer: don't include disabled syscall name in panics

2020-06-16 16:10:59 +02:00

testing.go

prog: refactor target.MakeMmap

2020-04-18 14:35:45 +02:00

workqueue.go

syz-fuzzer: don't break syscalls during minimization

2018-02-19 21:48:20 +01:00