diff options
| author | Mirko Covizzi <mrkcvzz@gmail.com> | 2025-04-24 21:49:39 +0200 |
|---|---|---|
| committer | Aleksandr Nogikh <nogikh@google.com> | 2025-04-25 08:01:08 +0000 |
| commit | dea5c7e43b28446926acb2fec04939e10f5cb835 (patch) | |
| tree | e58f5f7b8f4a41545a7fff422be56ec7494d8240 /docs | |
| parent | fe851ae118202c00a9640a322efde625607520af (diff) | |
docs/troubleshooting.md: fix typo
Fixes a typo.
Signed-off-by: Mirko Covizzi <mrkcvzz@gmail.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/troubleshooting.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 930adbc04..918c33746 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -21,7 +21,7 @@ Here are some things to check if there are problems running syzkaller. 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 prinths the `failed to copy binary` error shortly after VM has booted: + - 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 |