| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
When net.ifnames is set to 1, syzkaller might not be able to connect
to the virtual machines. Add the corresponding recommendations to the
documentation as well as a note to the troubleshooting guide.
|
| |
|
|
|
|
|
|
| |
It is now impossible to create a Debian Wheezy image (at least in a way
proposed by the documentation).
Instead, demonstrate how to create a Debian Buster image, the latest
version of Debian as for now.
|
| | |
|
| |
|
|
|
|
|
| |
Sandbox value needs quotes,
but we can simply drop sandbox as "none" is the default value.
Fixes #2526
|
| | |
|
| |
|
|
| |
Minor updates and readability improvements.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
setup_ubuntu-host_qemu-vm_x86-64-kernel.md recommends using
create_image.sh to create a Debian Stretch VM image. The script
configures the image assuming that the kernel will be booted with
predictable network device naming disabled, which syz-manager
currently does but the example qemu command in the setup document
does not.
To avoid confusing the user, add "net.ifnames=0" to the example qemu
command to disable predictable device naming. If not the VM fails to
bring up network interfaces and is then inaccessible via. ssh.
|
| |
|
|
|
| |
Clarify that the kernel build instructions refer to building the kernel
and not buildroot.
|
| |
|
|
|
|
|
|
|
|
| |
* Collecting kernel logs with dmesg over ssh doesn't work well and
sometimes we miss call traces when a crash occurs. Getting the kernel
log from a virtual serial port is much more effective.
* Creating linked clone VMs is faster then full clone VMs but it
requires snapshot management and this will bring more complexity to
syzkaller. Keep it simple and create full clone VMs for now.
* Use host-only networking because the VM gets its IP faster that way
|
| |
|
|
|
|
|
|
|
|
| |
The patch adding kcov support for riscv64 [1] was merged in the 5.9 merge
window (torvalds/linux@20d38f7c45a4). Adjust the docs accordingly to use
kernel 5.9-rc1.
[1] https://lore.kernel.org/linux-riscv/20200626124056.29708-1-tklauser@distanz.ch/
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We used command line arguments to select LSM beause
we did not have a good way to manage lots of configs.
The problem is that command line arguments are not
captures/provided with bug reports, so the configs
we provided could not reproduce the bug for developers.
We also had to duplicate .cmdline files 3 times.
Now that we have a good way to manager lots of configs,
embed LSM into the config.
Now that we have 3 configs also switch apparmor and smack
to SLUB. SLUB is the default for a very long time.
Leave SLAB only on selinux.
Update #2171
|
| |
|
|
|
|
|
|
| |
The shell and python scripts and config fragments are replaced
by the new config generation system (dashboard/config/linux/bits
and tools/syz-kconf).
Update #2171
|
| |
|
|
|
|
|
|
|
|
|
| |
There are too many assorted things in the config dir now.
Split them per-OS.
For now we just copy them to simplify deployment.
When syzbot instances are switched to new configs,
we can remove the old ones.
Update #2171
|
| |
|
|
|
|
|
| |
Use the "vmrun" utility to manage Workstation VMs. The syzkaller manager
creates temporary VMs (linked clones) from a base image, gets their IP
address and uses ssh to deploy and run programs (similar to the isolated
mode).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Add new page for fuzzing x86-64 Linux kernel on VMware VMs.
It explains how to create a VMDK image and how to run it on Ubuntu host
with Workstation installed. For now only the isolated mode of syzkaller
is supported.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
File types that we don't format automatically can end up
with such basic untidiness as trailing whitespaces.
Check for these. Remove all existing precedents.
|
| |
|
|
| |
Signed-off-by: Alexander Egorenkov <Alexander.Egorenkov@ibm.com>
|
| | |
|
| |
|
|
|
|
|
| |
As CONFIG_FAULT_INJECTION_USERCOPY is already included in linux-next,
enable the config.
Fixes #1979
|
| | |
|
| | |
|
| | |
|
| |
|
| |
There is a missing space on the command at line 131, which when copied causes it not to execute properly.
|
| |
|
|
|
|
|
|
| |
Use the OpenSBI "jump" firmware with the QEMU -bios parameter to boot
linux/riscv64. This will allow to boot the kernel directly without
having to recompile OpenSBI every time the kernel is recompiled.
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
|
| |
|
|
|
|
|
|
| |
Mention the possibility to use `-bios default` to use OpenSBI provided
with QEMU. However, this might not work on all distributions yet, so
make it optional.
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
|
| |
|
|
|
|
| |
buildroot already installs udhcpc as a DHCP client.
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
|
| |
|
|
| |
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
|
| |
|
|
|
|
|
|
|
|
| |
OpenSBI seems to be the recommended boot method nowadays, see e.g. [1],
[2]
[1] https://riscv.org/2019/01/risc-v-community-releases-opensbi-to-foster-continued-ecosystem-growth/
[2] https://wiki.freebsd.org/riscv#OpenSBI
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
|
| |
|
|
| |
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
|
| |
|
|
|
|
|
| |
Suggest to checkout linux kernel from kernel.org rather than from github.
github is a mirror and we don't use it ourselves and I think it's
generally not used by kernel developers. The kernel.org repo is
the canonical location.
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
|
| | |
|
| | |
|
| | |
|
| | |
|