aboutsummaryrefslogtreecommitdiffstats
path: root/docs/syzbot.md
diff options
context:
space:
mode:
authorDmitry Vyukov <dvyukov@google.com>2018-03-07 17:08:01 +0100
committerGitHub <noreply@github.com>2018-03-07 17:08:01 +0100
commitd50edb7e5cb52fbee77145ae4c2ff82470ee268a (patch)
tree0e8fbb432c5b164e7fe92accc7393ef60efdeca3 /docs/syzbot.md
parenta5e765400be062437431445e638dbb1774574e53 (diff)
Update syzbot.md
Diffstat (limited to 'docs/syzbot.md')
-rw-r--r--docs/syzbot.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/syzbot.md b/docs/syzbot.md
index e239a9e12..17b279e22 100644
--- a/docs/syzbot.md
+++ b/docs/syzbot.md
@@ -70,6 +70,14 @@ A syskaller program can also give you an idea as to what syscalls with what
arguments were executed (note that some calls can actually be executed in
parallel).
+A syzkaller program can be converted to an almost equivalent C source using `syz-prog2c` utility. `syz-prog2c` has lots of flags in common with [syz-execprog](https://github.com/google/syzkaller/blob/master/docs/executing_syzkaller_programs.md), e.g. `-threaded`/`-collide` which control if the syscalls are executed sequentially or in parallel. An example invocation:
+
+```
+syz-prog2c -prog repro.syz.txt -threaded -collide -repeat -procs=8 -sandbox=namespace -tun -tmpdir -waitrepeat
+```
+
+However, note that if `syzbot` did not provide a C reproducer, it wasn't able to trigger the bug using the C program (though, it can be just because the bug is triggered by a subtle race condition).
+
## Crash does not reproduce?
If the provided reproducer does not work for you, most likely it is related to the