diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2020-05-07 15:34:43 +0200 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2020-05-07 15:41:50 +0200 |
| commit | 413b991c26fa3ffadb04c4fe199dc3d1e1560232 (patch) | |
| tree | cf5dc1ac273938de421640b61c2857c7ebaf99bb /prog/rand.go | |
| parent | fa822db46ab32eb2cd92075f877e6eb1653a4f60 (diff) | |
syz-fuzzer: add more checks for disabled syscalls
We are seeing some panics that say that some disabled
syscalls somehow get into corpus.
I don't see where/how this can happen.
Add a check to syz-fuzzer to panic whenever we execute
a program with disabled syscall. Hopefull the panic
stack will shed some light.
Also add a check in manager as the last defence line
so that bad programs don't get into the corpus.
Diffstat (limited to 'prog/rand.go')
| -rw-r--r-- | prog/rand.go | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/prog/rand.go b/prog/rand.go index 019745161..b3d10cf42 100644 --- a/prog/rand.go +++ b/prog/rand.go @@ -379,7 +379,7 @@ func (r *randGen) createResource(s *state, res *ResourceType, dir Dir) (arg Arg, // TODO: reduce priority of less specialized ctors. var metas []*Syscall for _, meta := range metas0 { - if s.ct.enabled(meta.ID) { + if s.ct.Enabled(meta.ID) { metas = append(metas, meta) } } |