| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
|
| |
Consolidating FIDL library build mappings in one place, so that it can
be used from extraction, and script invoking fidlgen. This also makes
code clearer, and provides a more natural path for evolutions / dealing
with oddities.
Minor doc update post fx command changes.
|
| |
|
|
|
|
|
|
|
| |
Currently we have them duplicated in docs/configuration.md
and the actual source in pkg/mgrconfig/config.go.
Documentation is missing in one place or another,
some is outdated, some is phrased slightly differently.
Move all docs to pkg/mgrconfig/config.go and reference it
from docs/configuration.md instead.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Similar to C offsetof gives offset of a field
from the beginning of the parent struct.
We have several TODOs in descriptions asking for this.
|
| |
|
|
| |
This allows to use len[syscall:arg] expressions.
|
| |
|
|
|
|
|
|
|
|
| |
This change adds compiler support for complex path
expressions in len targets. E.g. it allows to refer
to a sibling field as len[parent_struct:field:another_field].
See the docs change for details.
This is just a compiler change.
The feature is not yet supported by the prog package.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* vm: add bhyve support
bhyve is FreeBSD's native hypervisor. Because it is missing snapshot
support and user networking, some additional configuration on the host
is required. However, unlike QEMU on FreeBSD, bhyve can make use of
hardware virtualization features and is thus faster.
* docs/freebsd: document bhyve support
|
| | |
|
| |
|
|
| |
Thanks to Greg for making me aware of it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
Recently, fuchsia changed the build directory for Zircon and a couple of files. Now instead of build-zircon, we have x64.zircon.
|
| | |
|
| | |
|
| |
|
|
|
| |
Add syzbot favicon and log.
Authored by Tetsuo Handa.
|
| |
|
|
|
|
|
| |
We now have too many namespaces and bugs.
Main page takes infinity to load.
Also almost nobody is interested in more than 1 namespace.
So split main page per-namespaces.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Ptr type has special handling of direction (pointers are always input).
But buffer type missed this special case all the time.
Make buffer less special by aliasing to the ptr[array[int8]] type.
As the result buffer type can't have optional trailing "opt" attribute
because we don't have such support for templates yet.
Change such cases to use ptr type directly.
Fixes #1097
|
| |
|
|
|
| |
svn commit 231296 matches commit d29e939c63b71 ("Add fuzzing coverage support") in the gcc git. The change is part of gcc 6.1.0.
Replace the svn commit number with a gcc version which everyone can easily compare.
Related links: https://github.com/torvalds/linux/commit/58f4df3c1bde999574d3e66b20eb7ee796a2647e#diff-4552954e64a20391a1a3b5fd3e494bc3
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This commit updates the documentation for fuchsia, updating both the fx
set commands as well as the syz-manager config example.
The invocation for the fx set command changed recently. The new command
requires the user to specify both the product and board (core.x64 and
core.arm64), as well as the build directory (otherwise everything gets
built into `out/default`).
The changes in the syz-manager config are for it to point to the right
files required to run a fuchsia vm.
|
| |
|
| |
Div's seem to work. Use them.
|
| |
|
| |
The previous attempt made things only worse... Try 2.
|
| |
|
|
|
| |
Add shorter anchors that does not depend on actual text (subject to change).
This allows to generate shorter stable links to docs.
Let's see if this syntax works.
|
| |
|
|
|
|
|
|
|
| |
Recently the fuchsia team decided to merge all their subrepos into one
big git repo. This meant that the "zircon" repo doesn't exist anymore.
Instead almost everything is under the fuchsia repo.
This change updates all the reference I could find in the code that
point to the zircon and docs repo to make them point to the new fuchsia
repo.
|
| |
|
| |
change chown to chmod
|
| | |
|
| |
|
|
| |
Update #501
|
| | |
|
| |
|
|
|
|
|
|
| |
Differences in code formatting between Go versions cause constant
problems for us (https://github.com/golang/go/issues/25161).
Currently we support 1.9 and 1.10. Switch to newer 1.11 and 1.12.
Fixes #1013
|
| |
|
|
|
|
| |
Extend doc on descriptions, const generation process,
add more links to internals, explain programs, etc.
Clarify that all generated files are checked in.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The setup instructions now reflect the steps needed to fuzz a recent
FreeBSD-CURRENT system. The previous instructions were written for
11.0-era FreeBSD and can be simplified. Steps required only on older
versions (e.g., 11.2 or 12.0) can be re-added if there is demand, but it
is expect that most syzkaller users are FreeBSD developers running
-CURRENT.
- Remove completed TODOs.
- Document how to build and install a KCOV-enabled kernel.
- Update set-up steps for a FreeBSD host. The newly added llvm metaport
makes it unnecessary to compile clang-format. The stock QEMU package
works fine on FreeBSD-CURRENT and it is not necessary to compile QEMU
binaries anymore.
- Document steps for preparing an image to be fuzzed under GCE as well
as QEMU. (The required steps are identical aside from syz-manager
configuration.)
|
| |
|
|
|
|
| |
* Adding recent bugs
* Follow Linux format of KASAN attribution
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This change makes all syz-execprog, syz-prog2c and syz-stress accept
-enable and -disable flags to enable or disable additional features
(tun, net_dev, net_reset, cgroups and binfmt_misc) instead of having
a separate flag for each of them.
The default (without any flags) behavior isn't changed: syz-execprog
and syz-stress enabled all the features (provided the runtime supports
them) and syz-prog2c disables all of them.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* Add description for setting up FreeBSD host
* Fix typo
* Fix comments provided by Dmitry
|
| |
|
|
|
| |
When committing the fix the the FreeBSD repo, I missed the line
stating that the issue was found by running syzkaller. So this
entry was missed...
|