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 | |
|---|---|---|
| .cargo | 1 month ago | |
| .github | 4 weeks ago | |
| .vim | 3 years ago | |
| .vscode | 8 months ago | |
| assets | 3 years ago | |
| aya | 4 weeks ago | |
| aya-build | 1 month ago | |
| aya-ebpf-macros | 1 month ago | |
| aya-log | 1 month ago | |
| aya-log-common | 1 month ago | |
| aya-log-ebpf-macros | 1 month ago | |
| aya-log-parser | 8 months ago | |
| aya-obj | 4 weeks ago | |
| aya-tool | 1 month ago | |
| ebpf | 4 weeks ago | |
| ebpf-panic | 8 months ago | |
| test | 4 weeks ago | |
| test-distro | 1 month ago | |
| xtask | 4 weeks ago | |
| .gitignore | 2 years ago | |
| .gitmodules | 2 years ago | |
| .markdownlint-cli2.yaml | 2 years ago | |
| .mergify.yml | 8 months ago | |
| .taplo.toml | 8 months ago | |
| AGENTS.md | 1 month ago | |
| Brewfile | 1 month ago | |
| CODE_OF_CONDUCT.md | 5 months ago | |
| CONTRIBUTING.md | 2 years ago | |
| Cargo.toml | 1 month ago | |
| LICENSE-APACHE | 5 years ago | |
| LICENSE-MIT | 5 years ago | |
| README.md | 8 months ago | |
| clippy.sh | 1 month ago | |
| netlify.toml | 8 months ago | |
| release.toml | 8 months ago | |
| rustfmt.toml | 2 years ago | |
README.md
API Documentation
Community
Join the conversation on Discord to discuss anything related to Aya or discover and contribute to a list of Awesome Aya projects.
Overview
eBPF is a technology that allows running user-supplied programs inside the Linux kernel. For more info see What is eBPF.
Aya is an eBPF library built with a focus on operability and developer experience. It does not rely on libbpf nor bcc - it's built from the ground up purely in Rust, using only the libc crate to execute syscalls. With BTF support and when linked with musl, it offers a true compile once, run everywhere solution, where a single self-contained binary can be deployed on many linux distributions and kernel versions.
Some of the major features provided include:
- Support for the BPF Type Format (BTF), which is transparently enabled when supported by the target kernel. This allows eBPF programs compiled against one kernel version to run on different kernel versions without the need to recompile.
- Support for function call relocation and global data maps, which allows eBPF programs to make function calls and use global variables and initializers.
- Async support with both tokio and async-std.
- Easy to deploy and fast to build: aya doesn't require a kernel build or compiled headers, and not even a C toolchain; a release build completes in a matter of seconds.
Example
Aya supports a large chunk of the eBPF API. The following example shows how to
use a BPF_PROG_TYPE_CGROUP_SKB program with aya:
use std::fs::File;
use aya::Ebpf;
use aya::programs::{CgroupSkb, CgroupSkbAttachType, CgroupAttachMode};
// load the BPF code
let mut ebpf = Ebpf::load_file("ebpf.o")?;
// get the `ingress_filter` program compiled into `ebpf.o`.
let ingress: &mut CgroupSkb = ebpf.program_mut("ingress_filter")?.try_into()?;
// load the program into the kernel
ingress.load()?;
// attach the program to the root cgroup. `ingress_filter` will be called for all
// incoming packets.
let cgroup = File::open("/sys/fs/cgroup/unified")?;
ingress.attach(cgroup, CgroupSkbAttachType::Ingress, CgroupAttachMode::AllowOverride)?;
Contributing
Please see the contributing guide.
License
Aya is distributed under the terms of either the MIT license or the Apache License (version 2.0), at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.