| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
The existing build lacked some headers, which prevented us from being
able to configure newer kernels.
|
| |
|
|
|
|
| |
Until KMSAN compiler API is finalized, we often need to use ToT Clang to
build the kernel. Download the latest compiler build from GS, and put it
under /syzkaller/clang-kmsan.
|
| |
|
|
|
|
|
| |
Our policy is to support 2 latest releases of Go.
Currently this is Go 1.16 and 1.17.
So update the old-env to the oldest release.
This will allow us to use lots of goodness available in the latest versions.
|
| |
|
|
|
|
| |
Clang 12 is the latest version supported for Ubuntu 12.04.
Update to this version.
There is no pressing need, but clang 10 is quite old, so update to the latest version.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This flag is needed for Bullseye that we use in env/syzbot containers.
I proactively added it to old-env as well assuming it's version-independent flag.
But Ubuntu 16.04 does not like this flag:
E: Command line option --allow-releaseinfo-change is not understood in combination with the other options
The command '/bin/sh -c apt-get update --allow-releaseinfo-change' returned a non-zero code: 100
Remove it from old-env.
|
| |
|
|
|
| |
We've switched to Go 1.16 toolchain for dashboard/app,
so don't need to test build with Go 1.11/12 anymore.
|
| |
|
|
|
|
| |
Currently we use the default distro Go, which is 1.15 in Bullseye.
Switch to 1.17 which has register-based calling convention and is
significantly faster.
|
| |
|
|
|
|
| |
The gcc 8 and clang 7 provided by buster are too old to build kernel.
Gcc 8 does not support MTE anymore and clang 7 is plain unsupported.
Update to bullseye which provides gcc 10 and clang 11.
|
| |
|
|
|
|
| |
Debian Buster provides only clang-7 which is quite old,
in particular it does not detect some warnings that later fire on OpenBSD.
Install clang-14 from https://apt.llvm.org.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Without this flag I am getting:
D: Repository 'http://security.debian.org/debian-security
buster/updates InRelease' changed its 'Suite' value
from 'stable' to 'oldstable'
Error: Process completed with exit code 100.
|
| |
|
|
|
|
|
| |
The debian repo contains an old version and it can't build gVisor:
external/rules_pkg/private/pkg_files.bzl:315:12: name 'json' is not defined
Signed-off-by: Andrei Vagin <avagin@google.com>
|
| |
|
|
|
| |
Not really GRTE, but it's enough to run some
scripts that hardcode the path.
|
| |
|
|
| |
Update #2446
|
| |
|
|
|
|
| |
It's used by kernel/gen_kheaders.sh.
Update #2096
|
| |
|
|
| |
Update #2096
|
| |
|
|
|
| |
Don't install grub packages, grub is not working inside of containers.
Add psmisc for ps.
|
| |
|
|
|
|
| |
A new image required to build i386 executables in bullseye.
We also need syzkaller user for sandboxing.
And EDITOR is not necessary as the container is not used interactively.
|
| | |
|
| |
|
|
|
|
| |
Use syz-old-env because it contains Go 1.14.
syz-env contains Go 1.15 and go-fuzz is broken with Go 1.15:
https://github.com/dvyukov/go-fuzz/issues/294
|
| |
|
|
|
| |
Go 1.15 is the latest release and it finds new bugs.
Leave old-env on 1.14 so that we test with both.
|
| |
|
|
|
|
| |
Also update sy-env to be able to build the root image inside.
Signed-off-by: Alexander Egorenkov <Alexander.Egorenkov@ibm.com>
|
| |
|
|
|
| |
Some users don't have access to the gcr.io registry.
Mirror images on github as well.
|
| |
|
|
|
|
|
| |
old-env is based on Ubuntu 16.04 and allows to test
executor build on older distributions.
Fixes #2055
|
| |
|
|
| |
qemu-user allows to run cross-arch binaries in tests.
|
| |
|
|
|
| |
Fix all errors it points to.
The one in netlink_send_ext is concerning.
|
| |
|
|
|
|
|
|
| |
Otherwise go-fuzz-build now fails with:
+ go-fuzz-build -libfuzzer -func FuzzDeserialize -o fuzzer.a ./prog/test
-: cannot find package "." in:
/syzkaller/gopath/src/github.com/google/syzkaller/vendor/github.com/dvyukov/go-fuzz/go-fuzz-dep
|
| | |
|
| |
|
|
| |
These arches are in-progress now. Need them in the image.
|
| |
|
|
|
|
|
|
| |
Since we now have SOURCEDIR_{FUCHSIA,AKAROS,NETBSD} exported in the
syz-big-env docker image, this will make CI fail for broken cross-builds too.
Update instructions in the docker image to fix the current problem
with permissions in syz-big-env: we need to tar with --mode=go=u.
|
|
|
On top of syz-env it provides akaros/fuchsia/netbsd toolchains and gcloud sdk.
With this it's possible to run dashboard/app tests on CI and locally
and test executor build and pkg/{csource,cover} for these OSes.
Update #1765
|