aboutsummaryrefslogtreecommitdiffstats
path: root/docs/usage.md
diff options
context:
space:
mode:
authorAndrey Konovalov <andreyknvl@google.com>2017-10-27 15:09:26 +0200
committerAndrey Konovalov <andreyknvl@gmail.com>2017-10-27 15:39:00 +0200
commit80c748800e07c28955c3cf696e7eda464a3f0634 (patch)
treed06149d4d790a3a1a14d8203ade331dcc4540ac8 /docs/usage.md
parent06a268ea21e01e94e7b8ab8ee5a64a82165e304b (diff)
docs: assorted improvements
Diffstat (limited to 'docs/usage.md')
-rw-r--r--docs/usage.md3
1 files changed, 0 insertions, 3 deletions
diff --git a/docs/usage.md b/docs/usage.md
index 6925c233a..308c8583f 100644
--- a/docs/usage.md
+++ b/docs/usage.md
@@ -11,9 +11,6 @@ The `syz-manager` process will wind up VMs and start fuzzing in them.
The `-config` command line option gives the location of the configuration file, which is [described here](configuration.md).
Found crashes, statistics and other information is exposed on the HTTP address specified in the manager config.
-At this point it's important to ensure that syzkaller is able to collect code coverage of the executed programs (unless you specified `"cover": false` in the config).
-The `cover` counter on the web page should be non zero.
-
## Crashes
Once syzkaller detected a kernel crash in one of the VMs, it will automatically start the process of reproducing this crash (unless you specified `"reproduce": false` in the config).