This looks really cool. Like all eBPF though, what sort of eBPF verification is it doing and is it possible to do the verification in CI?
With eBPF the common gotcha is you can compile totally invalid eBPF code, with no compile errors, only to find out at go time (and only to be able to find out at go time).
I happen to work on a system-wide profiler[1] that is eBPF-based, and what we do is load our bpf programs on various kernels[2] using qemu. This is important as the jit and verifier change significantly across kernel versions and we want to make sure we maintain compatibility.
Comments
This looks really cool. Like all eBPF though, what sort of eBPF verification is it doing and is it possible to do the verification in CI?
With eBPF the common gotcha is you can compile totally invalid eBPF code, with no compile errors, only to find out at go time (and only to be able to find out at go time).
I happen to work on a system-wide profiler[1] that is eBPF-based, and what we do is load our bpf programs on various kernels[2] using qemu. This is important as the jit and verifier change significantly across kernel versions and we want to make sure we maintain compatibility.
[1] https://github.com/parca-dev/parca-agent
[2] https://github.com/parca-dev/parca-agent/blob/54434c02773a8a...
Thanks!
This project can use a standalone eBPF verifier in this project: https://github.com/vbpf/ebpf-verifier
It can also use kernel verifier to verify the programs, then “offload”the BPF byte code from kernel, and runs it in userspace.