| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
When running the executor tests, do not rely on qemu-user providing
binfmt_misc handlers for alien arches (e.g. arm64 on x86), because
binfmt_misc cannot be mounted inside the Docker container.
Instead, explicitly run the cross-compiled executor under the
corresponding QEMU binary.
|
| |
|
|
|
| |
When running on Github CI, turn every failure to start a cross-arch binary
(e.g. due to missing qemu-user) into a fatal error.
|
| |
|
|
|
|
|
| |
Previously, cross-platform invocations of `syz-executor test` were ignored
in the case of a SYZFAIL, and the test was still marked as PASS.
Explicitly report a test failure instead.
|
| | |
|
| |
|
|
|
| |
On 32 core machines, we spin up 32 executor procs per each subtest.
In many cases, we don't need that many.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We see some errors of the form:
SYZFAIL: coverage filter is full
pc=0x80007000c0008 regions=[0xffffffffbfffffff 0x243fffffff 0x143fffffff 0xc3fffffff] alloc=156
Executor shouldn't send non kernel addresses in signal,
but somehow it does. It can happen if the VM memory is corrupted,
or if the test program does something very nasty (e.g. discovers
the output region and writes to it).
It's not possible to reliably filter signal in the tested VM.
Move all of the filtering logic to the host.
Fixes #4942
|
| | |
|
| |
|
|
|
| |
Fail some features in various ways for test OS,
and check that features are detected properly.
|
|
|
Move all syz-fuzzer logic into syz-executor and remove syz-fuzzer.
Also restore syz-runtest functionality in the manager.
Update #4917 (sets most signal handlers to SIG_IGN)
|
