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.
Go to file
Michal Rostecki 84e5e2894f aya-log: Unify IP format hints into one, repsesent it by `:i` token
Having separate format hints and tokens per IP address family is
unnecessary, since they are represented by different types and we handle
format hints for each type separately. So we can just have one format
hint.

Also, we should be consistent with the format strings grammar in
Rust[0]. The `type` token, which is mapped to formatting traits, usually
consists of one letter[1] (and optional `?` for `Debug` trait, but that
doesn't matter for us). It shouldn't consist of multiple letters. Our
`:ipv4` and `:ipv6` tokens were clearly breaking that convention, so we
should rather switch to something with one letter - hence `:i`.

[0] https://doc.rust-lang.org/std/fmt/#syntax
[1] https://doc.rust-lang.org/std/fmt/#formatting-traits
1 year ago
.cargo integration-tests: run on macos to get nested virtualization 2 years ago
.github Build tests with all features 2 years ago
.vim Re-organize into a single workspace 2 years ago
.vscode Re-organize into a single workspace 2 years ago
assets readme: Add crabby, sync with aya/README.md 2 years ago
aya fix(lint): remove useless `any` `all` in cfg. 1 year ago
aya-bpf-macros docs(macros): add rust docs for cgroup_sock_addr macro (#566) 2 years ago
aya-log aya-log: Unify IP format hints into one, repsesent it by `:i` token 1 year ago
aya-log-common aya-log: Unify IP format hints into one, repsesent it by `:i` token 1 year ago
aya-log-ebpf-macros aya-log: Unify IP format hints into one, repsesent it by `:i` token 1 year ago
aya-log-parser aya-log: Unify IP format hints into one, repsesent it by `:i` token 1 year ago
aya-obj Fix load errors for empty (but existent) BTF/BTF.ext sections (#608) 1 year ago
aya-tool build(deps): update bindgen requirement from 0.64 to 0.65 2 years ago
bpf feat(aya-log): check format and value type in proc macro 1 year ago
test aya-log: Unify IP format hints into one, repsesent it by `:i` token 1 year ago
xtask Merge pull request #598 from nak3/add-user_regs_strct 2 years ago
.gitignore Support using handle in tc programs 2 years ago
CODE_OF_CONDUCT.md Add a Code of Conduct 2 years ago
CONTRIBUTING.md Update CONTRIBUTING.md to link to the test/README.md 2 years ago
Cargo.toml integration-tests: Build eBPF programs always with release profile 2 years ago
LICENSE-APACHE Add license files 4 years ago
LICENSE-MIT Add license files 4 years ago
README.md Fix Aya build badge 2 years ago
netlify.toml Unpin Rust nightly 2 years ago
release.toml release.toml: fix pre/post release templates 2 years ago
rustfmt.toml Add rustfmt.toml 4 years ago

README.md

Aya

Crates.io License Build status Book

API Documentation

Unreleased Documentation Documentaiton

Community

Discord Awesome

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.