From e16e2c9a4cb6937323e861b646792a6c4c978a3c Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Tue, 4 Jun 2024 12:55:41 +0200 Subject: executor: add runner mode Move all syz-fuzzer logic into syz-executor and remove syz-fuzzer. Also restore syz-runtest functionality in the manager. Update #4917 (sets most signal handlers to SIG_IGN) --- docs/setup_syzbot.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'docs/setup_syzbot.md') diff --git a/docs/setup_syzbot.md b/docs/setup_syzbot.md index 060efcc6d..b6c05b00b 100644 --- a/docs/setup_syzbot.md +++ b/docs/setup_syzbot.md @@ -4,7 +4,9 @@ This doc will be useful to you: - should you wish to hack on user interface bits like the dashboard / mailing list integration or - should you wish to continuously run a separate syzbot dashboard for your own kernels -Note: For most development purposes you don't need a full syzbot setup. The meat of syzkaller is really located in syz-manager, syz-fuzzer and syz-executor. You can run syz-manager directly which is usually what you will want to do during fuzzer development. [See this documentation for syz-manager setup instructions](setup.md). +Note: For most development purposes you don't need a full syzbot setup. The meat of syzkaller is really located +in syz-manager and syz-executor. You can run syz-manager directly which is usually what you will want to do during +fuzzer development. [See this documentation for syz-manager setup instructions](setup.md). This doc assumes that you: - have a GCP account and billing setup @@ -366,4 +368,4 @@ sudo journalctl -fu syz-ci ``` gcloud app browse --project=$PROJECT ``` -Once syzkaller finds the first crashes they should show up here. This might take a while. \ No newline at end of file +Once syzkaller finds the first crashes they should show up here. This might take a while. -- cgit mrf-deployment