diff options
| author | Aleksandr Nogikh <nogikh@google.com> | 2022-11-24 11:51:15 +0100 |
|---|---|---|
| committer | Aleksandr Nogikh <wp32pw@gmail.com> | 2022-11-24 12:09:47 +0100 |
| commit | 3b903dad230946cfd32b986bc32d44fc23eaafd1 (patch) | |
| tree | cc3818bc2da0c738690d2bc300ca56f202424424 /docs/troubleshooting.md | |
| parent | ff68ff8f0e1a62984fe933655e14994ae3e16809 (diff) | |
tools: upgrade Buildroot image version
There are two reasons:
- The 2022.02 version does not longer build with the latest versions of
the build tools.
- The latest version was tested to work fine with the scp changes that
came with OpenSSH 9.0 (the use of the SFTP protocol).
Document the problem with scp in the troubleshooting guide.
Diffstat (limited to 'docs/troubleshooting.md')
| -rw-r--r-- | docs/troubleshooting.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 4a248b71c..7b1d77b51 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -21,6 +21,12 @@ 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 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) |