From fe4122c3bf0b8032bbc19b12cf398adceba6286b Mon Sep 17 00:00:00 2001 From: Andrey Konovalov Date: Thu, 7 May 2020 20:48:17 +0200 Subject: docs: various updates all over --- docs/usage.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/usage.md') diff --git a/docs/usage.md b/docs/usage.md index a15aa1e78..53a5a49aa 100644 --- a/docs/usage.md +++ b/docs/usage.md @@ -8,7 +8,7 @@ Start the `syz-manager` process as: ``` 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). +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. ## Crashes @@ -24,10 +24,10 @@ If a reproducer is successfully found, it can be generated in one of the two for Syzkaller always tries to generate a more user-friendly C reproducer, but sometimes fails for various reasons (for example slightly different timings). In case syzkaller only generated a syzkaller program, there's [a way to execute them](reproducing_crashes.md) to reproduce and debug the crash manually. -## Reporting bugs +## Hub -Check [here](linux/reporting_kernel_bugs.md) for the instructions on how to report Linux kernel bugs. +In case you're running multiple `syz-manager` instances, there's a way connect them together and allow to exchange programs and reproducers, see the details [here](hub.md). -## Other +## Reporting bugs -[How to connect several managers via Hub](hub.md) +Check [here](linux/reporting_kernel_bugs.md) for the instructions on how to report Linux kernel bugs. -- cgit mrf-deployment