blob: 918c337468fb9b502d9e753674141d2227252012 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
# Troubleshooting
Here are some things to check if there are problems running syzkaller.
- Use the `-debug` command line option to make syzkaller print all possible debug output,
from both the `syz-manager` top-level program and the `syz-executor` instances.
With this option syzkaller will only run one VM instance.
- Use the `-vv N` command line option to increase the amount of logging output, from both
the `syz-manager` top-level program and the `syz-executor` instances (which go to the
output files in the `crashes` subdirectory of the working directory). Higher values of
N give more output.
- If logging indicates problems with the executor program (e.g. `executor failure`),
try manually running a short sequence of system calls:
- Copy `syz-executor` and `syz-execprog` into a running VM.
- In the VM run `./syz-execprog -executor ./syz-executor -debug sampleprog` where
sampleprog is a simple system call script (e.g. just containing `getpid()`).
- For example, if this reports that `clone` has failed, this probably indicates
that the test kernel does not include support for all of the required namespaces.
In this case, running the `syz-execprog` test with the `-sandbox=setuid` option fixes the problem,
so the main configuration needs to be updated to set `sandbox` to `setuid`.
- If syzkaller prints the `failed to copy binary` error shortly after VM has booted:
- If you're using Buildroot images and the error output contains the `subsystem request
failed on channel 0` line, this can be due to the [OpenSSH 9.0 changes](https://www.openssh.com/txt/release-9.0)
that force the use of the SFTP protocol. Upgrade your Buildroot image to the latest version and
make sure SFTP is enabled there.
Also see [this](linux/troubleshooting.md) for Linux kernel specific troubleshooting advice.
If none of the above helps, file a bug on [the bug tracker](https://github.com/google/syzkaller/issues)
or ask us directly on the syzkaller@googlegroups.com mailing list.
Please include syzkaller commit id that you use and `syz-manager` output with `-debug` flag enabled if applicable.
|
