mirror of https://github.com/aya-rs/aya
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.
f0a9f19ddc
Change FromRawTracepointArgs::arg to return T rather than *const T which seems to have been returning a dangling pointer. Arguably this is not strictly necessary; edition 2024 seems to be focused on increased strictness around unsafe code which doesn't unlock new functionality for our users. That said, this work revealed an apparent bug (see above) that we wouldn't otherwise catch due to allow-by-default lints. |
1 week ago | |
|---|---|---|
| .. | ||
| src | 1 week ago | |
| CHANGELOG.md | 5 months ago | |
| Cargo.toml | 1 week ago | |
| README.md | 1 year ago | |
| release.toml | 3 years ago | |
README.md
aya-log - a logging library for eBPF programs
Overview
aya-log is a logging library for eBPF programs written using aya. Think of
it as the log crate for eBPF.
Installation
User space
Add aya-log to Cargo.toml:
[dependencies]
aya-log = { git = "https://github.com/aya-rs/aya", branch = "main" }
eBPF side
Add aya-log-ebpf to Cargo.toml:
[dependencies]
aya-log-ebpf = { git = "https://github.com/aya-rs/aya", branch = "main" }
Example
Here's an example that uses aya-log in conjunction with the env_logger crate
to log eBPF messages to the terminal.
User space code
use aya_log::EbpfLogger;
env_logger::init();
// Will log using the default logger, which is TermLogger in this case
EbpfLogger::init(&mut bpf).unwrap();
eBPF code
use aya_log_ebpf::info;
fn try_xdp_firewall(ctx: XdpContext) -> Result<u32, ()> {
if let Some(port) = tcp_dest_port(&ctx)? {
if block_port(port) {
info!(&ctx, "❌ blocked incoming connection on port: {}", port);
return Ok(XDP_DROP);
}
}
Ok(XDP_PASS)
}