79c9489a4f
For unclear reasons, two of the integration tests related to uprobes were resolving a symbol in libc. The integration-test binary can be built statically, in which case it would not load or reference libc. Statically linking the integration tests and running them in a VM without a userland is a convenient mechanism to exercise the tests against different kernel versions. The fact that the statically linked integration-test binary does not load libc is not the only reason these tests failed in such an environment. In fact, the logic to look in the process's memory maps was not running (because no pid was being passed). Separate logic to determine which object file to use when attempting to resolve a symbol for attaching a uprobe changes its behavior based on whether that target is an absolute path. If the target is not an absolute path, the code searches through the LdSoCache. This cache does not always exist in linux systems; when an attach call is made with a relative path target and there is no /etc/ld.so.cache file, the attach call will fail. This commit does not change that behavior, it merely sidesteps it. |
2 years ago | |
---|---|---|
.cargo | 2 years ago | |
.github | 2 years ago | |
.vim | 3 years ago | |
.vscode | 2 years ago | |
assets | 3 years ago | |
aya | 2 years ago | |
aya-bpf-macros | 2 years ago | |
aya-log | 2 years ago | |
aya-log-common | 2 years ago | |
aya-log-ebpf-macros | 2 years ago | |
aya-log-parser | 2 years ago | |
aya-obj | 2 years ago | |
aya-tool | 2 years ago | |
bpf | 2 years ago | |
test | 2 years ago | |
xtask | 2 years ago | |
.gitignore | 2 years ago | |
.gitmodules | 2 years ago | |
.mergify.yml | 2 years ago | |
.taplo.toml | 2 years ago | |
CODE_OF_CONDUCT.md | 3 years ago | |
CONTRIBUTING.md | 2 years ago | |
Cargo.toml | 2 years ago | |
LICENSE-APACHE | 4 years ago | |
LICENSE-MIT | 4 years ago | |
README.md | 2 years ago | |
netlify.toml | 2 years ago | |
release.toml | 2 years 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 https://ebpf.io/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::Bpf;
use aya::programs::{CgroupSkb, CgroupSkbAttachType};
// load the BPF code
let mut bpf = Bpf::load_file("bpf.o")?;
// get the `ingress_filter` program compiled into `bpf.o`.
let ingress: &mut CgroupSkb = bpf.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)?;
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.