Skip to content

Updating the README to run the fuzzer #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zhanggenex wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Updating the README to run the fuzzer #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c0e9737
Updating the README to run the fuzzer
zhanggenex May 11, 2025
803bff8
Update README.md
zhanggenex May 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,11 @@ QEMU images, and Monarch source code.
./scripts/complete-cfg.sh
```

And a linux configuration is necessary：
```bash
sudo sysctl vm.overcommit_memory=1
```

Now, pick up one of the configurations and run Monarch with it. For example,
```bash
$ sudo ./src/bin/syz-manager -config fuzz-config/eval-config/non-fault-mode/nfs/nfs-c-normal.cfg
Expand All @@ -126,7 +131,11 @@ If you can see the `executed xxx` from the terminal,
it means the Monarch is running successfully.
Now, you can continue the following evaluations.

> **Note**: Once you start a fuzzing instance, it keeps running until you manually stop (CTRL+C or KILL) it.
> **Note1**: Once you start a fuzzing instance, it keeps running until you manually stop (CTRL+C or KILL) it.

> **Note2**: Users can add '-debug' in the starting fuzzing command to see detailed debug information in case of issues in running the fuzzer.

> **Note3**: When debug prints "Connection refused", please check the IP address of br0 with ifconfig. It should be 192.168.0.1/24. A specific unkown procedure changes the IP periodically, so users should check the IP address often.

### Bug-finding (Section 5.1)

Expand Down