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

Friday Ortiz 51d97a4303 test,xtask: include debug symbols for attaching breakpoints in tests For some reason, the aarch64 6.1 debian kernel was not compiled with CONFIG_KALLSYMS_ALL=y, and the locations of globals are not available in kallsyms. To attach breakpoints to these symbols in the test pipeline, we need to read them from System.map and apply the kaslr offset to get their real address. The System.map file is not provided in the kernel package by default, so we need to extract it from the corresponding debug package. - .github: pull the corresponding debug packages down as well as regular kernels - test: attach the perf_event_bp test breakpoint to the modprobe_path address in kallsyms if present, or by applying the kaslr offset to the System.map address if not found - xtask: preferentially extract the System.map file from the debug package, if available		4 weeks ago
..
integration-common	aya,ebpf: add BPF_MAP_TYPE_SK_STORAGE	1 month ago
integration-ebpf	test: add a perf_event breakpoint test	4 weeks ago
integration-test	test,xtask: include debug symbols for attaching breakpoints in tests	4 weeks ago
.gitignore	test: Replace RTF with Rust	3 years ago
README.md	ci: cache downloads	11 months 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 --cache-dir <CACHE_DIR> <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.