docs: add landing page for automatically reported bugs

1 files changed, 27 insertions, 0 deletions

diff --git a/docs/syzbot.md b/docs/syzbot.md
new file mode 100644
index 000000000..69d67686d
--- /dev/null
+++ b/docs/syzbot.md
@@ -0,0 +1,27 @@
+# syzbot
+
+`syzbot` system continuously fuzzes main Linux kernel branches and automatically
+reports all found bugs. Direct all questions to syzkaller@googlegroups.com.
+
+## syzkaller reproducers
+
+`syzbot` aims at providing stand-alone C reproducers for all reported bugs.
+However, sometimes it can't extract a reproducer at all, or can only extract a
+syzkaller reproducer. syzkaller reproducers are programs in a special syzkaller
+notation and they can be executed on the target system with a little bit more
+effort. See [this](https://github.com/google/syzkaller/blob/master/docs/executing_syzkaller_programs.md)
+for instructions.
+
+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).
+
+## Crash does not reproduce?
+
+Sometimes the provided reproducers do not work. Most likely it is related to the
+fact that you have slightly different setup than `syzbot`. `syzbot` has obtained
+the provided crash report on the provided reproducer on a freshly-booted
+machine, so the reproducer worked for it somehow.
+
+If the reproducer exits quickly, try to run it several times, or in a loop.
+There can be some races involved.