| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Syscall attributes are extended with a fsck command field which lets
file system mount definitions specify a fsck-like command to run. This
is required because all file systems have a custom fsck command
invokation style.
When uploading a compressed image asset to the dashboard, syz-manager
also runs the fsck command and logs its output over the dashapi.
The dashboard logs these fsck logs into the database.
This has been requested by fs maintainer Ted Tso who would like to
quickly understand whether a filesystem is corrupted or not before
looking at a reproducer in more details. Ultimately, this could be used
as an early triage sign to determine whether a bug is obviously
critical.
|
| |
|
|
| |
Useful for testing local Dockerfile changes that have not been pushed yet.
|
| |
|
|
|
|
|
| |
1. Get rid of executing_syzkaller_programs.md as it now mostly overlaps
with reproducing_crashes.md.
2. Update the instructions on building the kernel with syzbot compilers.
3. Update the links throughout the documentation.
|
| |
|
|
|
|
|
|
|
|
| |
Let's list all the possible ways of reproducing syzkaller crashes
locally and keep the instructions of how to manually craft a reproducer
at the bottom.
Add information about the ktest tooling - now it also automates the
reproduction of syzbot bugs. See the discussion at:
https://groups.google.com/g/syzkaller/c/UTPrWcJfS8Q/m/K1YXz-f1AQAJ
|
| |
|
|
|
|
|
|
|
|
|
| |
ex. f3 field has logic or operator in if condition:
conditional_struct {
mask int32
f1 field1 (if[value[mask] & FIELD_FLAG1])
f2 int64 (if[value[mask] & FIELD_FLAG2])
f3 int64 (if[value[mask] == FIELD_FLAG1 || value[mask] == FIELD_FLAG2])
} [packed]
|
| | |
|
| |
|
|
|
|
|
| |
In some situations, it could be useful to share access to the dashboard
to multiple authentication domains. The current GlobalConfig format
doesn't really allow it so this deprecates the existing field and add a
new slice of allowed authentication domains.
|
| |
|
|
|
|
|
| |
go.mod has been bumped with go 1.22.1 version recently.
So let's update the documentation as well.
https://github.com/google/syzkaller/blob/master/docs/linux/setup.md#go-and-syzkaller
|
| |
|
|
| |
Add more guidelines and be more concrete.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
act(https://github.com/nektos/act) is used to build github workflow locally.
When running `act -j build` in local host, it reports:
exec failed: unable to start container process: exec: "node": executable file
not found in $PATH: unknown.
Adding nodejs package can fix the build error.
Updated docs with act usage too.
|
| | |
|
| |
|
|
| |
Finish the translation of docs/linux/reporting_kernel_bugs.md, which has also been proofread by HCTT translation group.
|
| |
|
|
|
|
| |
linux/setup_linux-host_qemu-vm_arm64-kernel.md
Upload translation of linux/setup_linux-host_qemu-vm_arm64-kernel.md, which is proofread by HCTT.
|
| |
|
|
|
|
| |
This is no longer a standalone tool, but rather a syz-manager mode.
Closes #4970.
|
| |
|
|
| |
executing_syzkaller_programs.md
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Finish the translation of docs/syscall_descriptions_syntax.md, which has also been proofread by HCTT translation group.
|
| | |
|
| |
|
|
|
|
| |
Finish the translation of docs/contributing.md, which has also been proofread by HCTT translation group.
Please note that pr https://github.com/google/syzkaller/pull/5038 is obsolete and closed, so please ignore it.
|
| |
|
|
|
|
| |
Finish the translation of linux/external_fuzzing_network.md.
Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
|
| | |
|
| |
|
|
| |
Fix a typo in the section of "Using syz-env": expacted to expected.
|
| | |
|
| |
|
|
| |
Fixed 'fmt' documentation description at docs/syscall_descriptions_syntax.md.
|
| |
|
|
| |
Closes #3802.
|
| | |
|
| |
|
|
|
|
|
| |
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)
|
| |
|
|
| |
Remove a redundant square bracket in section "Expression syntax".
|
| |
|
|
|
| |
In case of ARM64 bugs, we need to use a somewhat different set of qemu
arguments to run the kernel from syzbot assets locally.
|
| |
|
|
| |
strconst["foo"] was replaced by ptr[in, string["foo"]].
|
| | |
|
| |
|
|
|
|
| |
Update the descriptions to mark calls that cause remote coverage
collection.
Remote some hacky code from the executor.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Feature checking procedure is split into 2 phases:
1. syz-fuzzer invokes "syz-executor setup feature" for each feature one-by-one,
and checks if executor does not fail.
Executor can also return a special "this feature does not need custom setup",
this allows to not call setup of these features in each new VM.
2. pkg/vminfo runs a simple program with ipc.ExecOpts specific for a concrete feature,
e.g. for wifi injection it will try to run a program with wifi feature enabled,
if setup of the feature fails, executor should also exit with an error.
For coverage features we also additionally check that we actually got coverage.
Then pkg/vminfo combines results of these 2 checks into final result.
syz-execprog now also uses vminfo package and mimics the same checking procedure.
Update #1541
|
| |
|
|
|
|
|
| |
go:embed is a more modern way to do this and it does
not require a special Makefile step.
Since go:embed cannot use paths that contains "..",
the actual embeding is moved to executor package.
|
| |
|
|
|
|
|
|
| |
Move syz-stress logic into syz-execprog.
It's already doing most of what syz-stress could do,
it even can load a corpus since recently.
There are few remaining bits that are missing
in execprog, so add them to execprog.
|
| |
|
|
| |
Builds won't work with 1.20 anymore and the download steps below already mention 1.21.4, so adjust the text as well.
|
| | |
|
| |
|
|
| |
syz-fuzzer no longer generates programs.
|
| |
|
|
|
|
| |
Fix typo in syzbot.md.
Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
|
| |
|
|
|
|
| |
Add some short notes on how syz-db can also be used manually.
Signed-off-by: Simone Weiß <simone.weiss@elektrobit.com>
|
| |
|
|
| |
We don't reference it anywhere and we have the list right on the main page.
|
| |
|
|
|
|
|
| |
Akaros support is unused, it was shutdown on syzbot for a while,
the akaros development seems to be frozen for years as well.
We have a bunch of hacks for Akaros since it supported
only super old gcc and haven't supported Go. Remove it.
|
| |
|
|
|
|
|
|
| |
Delete support for odroid board.
It's build broken for >3 years (at least on 8ba8079b119f).
We keep it in history and if it's resurrected, it needs
to be merged with vm/isolated and most code needs to be
at least build-tested (mock out only the C interface).
|
| |
|
|
|
|
|
| |
The translation of program_syntax.md is done. There is no relative link
in the document, no worry about relocation.
Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
|
| |
|
|
|
|
|
|
|
|
| |
Finish the translation of docs/usage.md. Our current policy is
to keep the English link of untranslated documents.
Note that, all the relative paths of documents need relocation
since these documents may not be translated.
Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
|
| |
|
|
| |
The -> Then
|