ebpf
ebpf copied to clipboard
cilium
ebpf-go is a pure-Go library to read, modify and load eBPF programs and attach them to various hooks in the Linux kernel.
When a process uses several CollectionSpecs, `/proc/kallsyms` is read separately for each collection, which is inefficient. This PR adds a way to warm the kallsyms cache for all CollectionSpecs. ```...
When a map value contains a bpf_spin_lock field, the map could not be declared as `BPF_MAP_TYPE_LRU_HASH`. ``` struct value { struct bpf_spin_lock semaphore; // other fields } ``` This is...
### Describe the bug https://github.com/cilium/ebpf/commit/f086705551436bf5bd27d6dc0a22df8974b87ef2 breaks loading of programs with error: `decoding instructions for section : offset : invalid constant 0xffffffff` The actual instruction looks like `85 00 00 00...
See issue #1758 Has been used successfully in unvariance/collector#109, PR unvariance/collector#110. Tested in a dev container on MacOs and on a Linux bare metal box. Closes #1758
The library currently doesn't expose `ringbuf` and `perf` on Windows. Upstream has accepted a proposal on exposing an API which is very similar to Linux: https://github.com/microsoft/ebpf-for-windows/pull/3848 This will help porting....
## Background and Motivation Currently, the bpf2go tool only supports compiling a single source file at a time. This limits our ability to create modular eBPF programs composed of multiple...
We've been having regular hangs in CI, where one of the vimto based tests (usually 6.1 but not exclusively so) hangs for 10 minutes and then times out with a...
Both kernels are now EOL'd by kernel.org. Cilium documents that it requires at least 5.4 (or a RHEL equivalent). I propose that we remove 4.14 and 4.19 from CI but...
### Describe the bug If prog was jited after loading, PC offset of bpf pseudo call was stored at field `off`, not `imm`. please see below code for details https://github.com/torvalds/linux/blob/87a132e73910e8689902aed7f2fc229d6908383b/kernel/bpf/verifier.c#L20783-L20795...
### Describe the bug We get this flake every once in a while: ``` === FAIL: . TestStats (0.00s) info_test.go:362: expected a runtime other than 0ns ``` That number comes...