| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
Use a newer Buildroot release.
Use an appropriate arm instruction set for arm32.
Reduce the syslogd logging level.
Closes #5986.
Closes #5452.
|
| |
|
|
|
| |
It will enable Buildroot image usage also for the kenrels that don't
enable CONFIG_DEVTMPFS_MOUNT.
|
| |
|
|
|
|
|
|
|
|
| |
The newly built image resolves the following problem:
debug1: Sending subsystem: sftp
debug1: pledge: fork
subsystem request failed on channel 0
Also, ext2->ext4 transition allows to fuzz swap on arm32.
|
| |
|
|
|
|
|
|
| |
Our current buildroot can't be mounted by v5.3 kernels and older:
EXT4-fs (sda): couldn't mount RDWR because of unsupported optional features (8000)
This has caused lots of bad bisection results, see #3224. Our buildroot
must support very old kernels so we can test during cause bisections.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
create-buildroot-image.sh creates a minimal sshd_config, which does not
configure sftp. Thus, if the initial scp to setup syz-fuzzer uses sftp,
it fails with the error below, and syz-manager never starts fuzzing.
2022/09/06 16:03:44 failed to copy binary: failed to run
["scp" "-P" "14125" ... "/home/ec2-user/syzkaller/bin/linux_amd64/syz-fuzzer"
"root@localhost:/syz-fuzzer"]: exit status 255
Warning: Permanently added '[localhost]:14125' (ED25519) to the list of known hosts.
subsystem request failed on channel 0
Connection closed
We can see sftp throws the same sequences by manually running scp in
verbose mode.
$ scp -v -P 14125 /home/ec2-user/syzkaller/bin/linux_amd64/syz-fuzzer root@localhost:/syz-fuzzer
Executing: program /usr/bin/ssh host localhost, user root, command sftp
...
debug1: Connecting to localhost [localhost] port 14125.
debug1: Connection established.
...
debug1: Sending subsystem: sftp
subsystem request failed on channel 0
Connection closed
Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com>
|
| | |
|
| |
|
|
| |
Require Linux >= 5.10 instead of 5.15.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
2021.08.x does not build on Linux 5.15+ due to the following error.
interpret.c:48:10: fatal error: linux/ipx.h: No such file or directory
48 | #include <linux/ipx.h>
It was fixed in the newer buildroot versions.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently the following errors happen during boot:
mount: mounting mqueue on /dev/mqueue failed: No such file or directory
mount: mounting hugetlbfs on /dev/hugepages failed: No such file or directory
mount: mounting fuse.lxcfs on /var/lib/lxcfs failed: No such file or directory
Remove these mounts.
Mounting of /dev/mqueue and /dev/hugepages fails because these dirs don't exist
and the buildroot init does not create them for some reason. We can't pre-create
them because /dev is itself mounted as devtmpfs.
But we also don't need these mounts. Both mqueue and hugetlbfs are trivial to mount
and the fuzzer does not have problems mounting them locally and using (we have good
coverage anyway).
fuse.lxcfs is simply a fuse filesystem (".lxcfs" is ignored). We don't need to mount
an empty global fuse filesystem. And it won't work w/o a userspace server anyway.
|
| |
|
|
| |
It's not necessary any longer because now we're using binderfs.
|
|
|
We used to use Debian-based images, but they have several issues:
1. They boot too slowly (we don't need full systemd power).
2. Systemd mounts cgroup controllers so that we can't use them during fuzzing
(can be mounted only once).
3. We have poor control over contents of the image.
This script creates lightweight buildroot-based images that boot fast.
|
