You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

History

Michal Rostecki cbb2602c69 ebpf: Call `bpf_probe_read` on `*const T` BTF arguments It's necessary to call `bpf_probe_read` not only for pointers retrieved from `PtRegs`, but also from BTF arguments. `bpf_probe_read` might return an error, so the return type of `.arg()` methods in contexts handling BTF arguments changes from `T` to `Option<T>`. `None` is returned when `bpf_probe_read` call is not successful. Fixes: #542		5 months ago
..
integration-ebpf	ebpf: Call `bpf_probe_read` on `*const T` BTF arguments	5 months ago
integration-test	ebpf: Call `bpf_probe_read` on `*const T` BTF arguments	5 months ago
.gitignore	test: Replace RTF with Rust	3 years ago
README.md	tests: update instructions on setting up and running tests	1 year ago

Aya Integration Tests

The aya integration test suite is a set of tests to ensure that common usage behaviours work on real Linux distros

Prerequisites

You'll need:

From the root of this repository:

cargo xtask integration-test local

cargo xtask integration-test vm <KERNEL IMAGE>

Tests should follow these guidelines:

Rust eBPF code should live in integration-ebpf/${NAME}.rs and included in integration-ebpf/Cargo.toml and integration-test/src/lib.rs using include_bytes_aligned!.
C eBPF code should live in integration-test/bpf/${NAME}.bpf.c. It should be added to the list of files in integration-test/build.rs and the list of constants in integration-test/src/lib.rs using include_bytes_aligned!.
Tests should be added to integration-test/tests.
You may add a new module, or use an existing one.
Test functions should not return anyhow::Result<()> since this produces errors without stack traces. Prefer to panic! instead.