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 f48b5a4a84 aya: Ensure that truncated map names are NULL terminated Limit of map names in eBPF is 16 bytes and they have to be NULL terminated. Before this change, long names were truncated to 16 bytes. `MAP_WITH_LOOOONG_NAAAAAAAAME` would become `MAP_WITH_LOOOONG`, which doesn't contain the NULL byte. This change fixes that by truncating the name to 15 bytes, ensuring that the 16th byte is NULL. `MAP_WITH_LOOOONG_NAAAAAAAAME` is truncated to `MAP_WITH_LOOOON\0`.		2 days ago
..
integration-common	introduce workspace lints, warn on unused crates	1 week ago
integration-ebpf	aya: Ensure that truncated map names are NULL terminated	2 days ago
integration-test	introduce workspace lints, warn on unused crates	1 week ago
.gitignore	test: Replace RTF with Rust	3 years ago
README.md	ci: cache downloads	3 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.