From 71f516782bb401fd3968fdfdb2d211f496cf73c1 Mon Sep 17 00:00:00 2001 From: Andrey Konovalov Date: Wed, 14 Jun 2017 17:03:53 +0200 Subject: docs: various improvements --- docs/process_structure.md | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 docs/process_structure.md (limited to 'docs/process_structure.md') diff --git a/docs/process_structure.md b/docs/process_structure.md deleted file mode 100644 index 1e5998328..000000000 --- a/docs/process_structure.md +++ /dev/null @@ -1,21 +0,0 @@ -# Process Structure - -The process structure for the syzkaller system is shown in the following diagram; -red labels indicate corresponding configuration options. - -![Process structure for syzkaller](process_structure.png?raw=true) - -The `syz-manager` process starts, monitors and restarts several VM instances (support for -physical machines is not implemented yet), and starts a `syz-fuzzer` process inside of the VMs. -It is responsible for persistent corpus and crash storage. As opposed to `syz-fuzzer` processes, -it runs on a host with stable kernel which does not experience white-noise fuzzer load. - -The `syz-fuzzer` process runs inside of presumably unstable VMs (or physical machines under test). -The `syz-fuzzer` guides fuzzing process itself (input generation, mutation, minimization, etc) -and sends inputs that trigger new coverage back to the `syz-manager` process via RPC. -It also starts transient `syz-executor` processes. - -Each `syz-executor` process executes a single input (a sequence of syscalls). -It accepts the program to execute from the `syz-fuzzer` process and sends results back. -It is designed to be as simple as possible (to not interfere with fuzzing process), -written in C++, compiled as static binary and uses shared memory for communication. -- cgit mrf-deployment