From c19ce525d8b8bbb454fd60909a14eb7f587eb08e Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Tue, 6 Aug 2024 16:23:23 +0200 Subject: docs: update information about syz-runtest This is no longer a standalone tool, but rather a syz-manager mode. Closes #4970. --- docs/linux/external_fuzzing_usb.md | 2 +- docs/syscall_descriptions.md | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) (limited to 'docs') diff --git a/docs/linux/external_fuzzing_usb.md b/docs/linux/external_fuzzing_usb.md index ee4c0a132..3615af7ed 100644 --- a/docs/linux/external_fuzzing_usb.md +++ b/docs/linux/external_fuzzing_usb.md @@ -36,7 +36,7 @@ These pseudo-syscalls targeted at a few different layers: There are [runtests](/sys/linux/test/) for USB pseudo-syscalls. They are named starting with the `vusb` prefix and can be run with: ``` -./bin/syz-runtest -config=usb-manager.cfg -tests=vusb +./bin/syz-manager -config usb-manager.cfg -mode run-tests -tests vusb ``` diff --git a/docs/syscall_descriptions.md b/docs/syscall_descriptions.md index fa1f41fbb..911232f08 100644 --- a/docs/syscall_descriptions.md +++ b/docs/syscall_descriptions.md @@ -280,13 +280,13 @@ It's always good to add a test at least for "the main successful scenario" for t It will ensure that the descriptions are actually correct and that it's possible for the fuzzer to come up with the successful scenario. See [io_uring test](/sys/linux/test/io_uring) as a good example. -The tests can be run with the `syz-runtest` utility as: +The tests can be run with the `run-tests` functionality of `syz-manager`: ``` -make runtest && bin/syz-runtest -config manager.config +make && bin/syz-manager -config manager.config -mode run-tests ``` -`syz-runtest` boots multiple VMs and runs these tests in different execution modes inside of the VMs. +It will boot multiple VMs and runs these tests in different execution modes inside of the VMs. -However, full `syz-runtest` run takes time, so while developing the test, it's more handy to run it +However, the full run takes significant time, so while developing the test, it's more handy to run it using the `syz-execprog` utility. To run the test, copy `syz-execprog`, `syz-executor` and the test into a manually booted VM and then run the following command inside of the VM: ``` -- cgit mrf-deployment