All notable changes to clj-ebpf will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
- Fixed Java 25 compatibility issue reading
/proc filesystem files. The
get-current-cgroup function now uses java.nio.file.Files/readString
instead of slurp, which fails on /proc files in Java 25 due to
FileInputStream.available() returning EINVAL for special filesystem files. - Fixed batch operations fallback logic checking wrong errno keyword.
The code was checking for
:inval but the syscall layer returns :einval.
Now map-lookup-batch, map-update-batch, map-delete-batch, and
map-lookup-and-delete-batch correctly fall back to individual operations
when the kernel doesn't support batch syscalls.
- Comprehensive BPF helper functions library documentation in README
- Helper functions tutorial (
examples/helpers_tutorial.clj) - Helper functions guide (
docs/guides/helpers-guide.md)
- Fixed ENOENT errno handling in map operations - map-keys, map-values,
map-entries, and map-count now work correctly on empty maps and when
iterating to the end of a map. Previously checked for :noent instead
of the correct :enoent errno keyword.
- Added test-enoent-handling test to verify ENOENT handling in map operations
- BREAKING: Migrated from JNA to Java's Panama Foreign Function & Memory API
- Requires Java 25+ (previously Java 11+)
- Zero external dependencies - removed JNA dependency entirely
- Uses MemorySegment instead of JNA Pointer/Memory
- More efficient native memory management with automatic cleanup
- Better performance through direct foreign function access
- No external dependencies - uses only Java standard library
- Better integration with modern Java features
- Improved memory safety with scoped allocations
- More efficient native calls through method handles
- Future-proof: Panama FFI is the official Java native interface going forward
- Direct
bpf() syscall interface using Panama FFI (Java 25+) - Complete BPF constants and enumerations from
linux/bpf.h - Memory management utilities for native interactions
- Kernel version detection and compatibility checking
- BPF filesystem operations
- Hash map support (BPF_MAP_TYPE_HASH)
- Array map support (BPF_MAP_TYPE_ARRAY)
- Ring buffer map support (BPF_MAP_TYPE_RINGBUF)
- Map lifecycle management (create, close)
- Core operations (lookup, update, delete)
- Map iteration (keys, values, entries)
- Map pinning/unpinning to BPF filesystem
- Custom key/value serializers and deserializers
- Resource management macros (
with-map) - Convenience constructors for common map types
- BPF program loading with verifier log capture
- Kprobe attachment (function entry)
- Kretprobe attachment (function return)
- Tracepoint attachment
- Raw tracepoint attachment
- Program pinning/unpinning
- Program lifecycle management (load, close)
- Resource management macros (
with-program) - Automatic attachment cleanup on program close
- Ring buffer consumer framework
- Event serialization/deserialization helpers
- Struct packing/unpacking utilities
- Event polling infrastructure
- Idiomatic Clojure APIs
- Comprehensive error handling with errno translation
- Detailed verifier log capture and reporting
- System capability checking
- Kernel version compatibility checks
- Extensive documentation and examples
- REPL-friendly development workflow
- Unit tests for constants and utilities
- Integration tests for maps (requires Linux + BPF)
- Integration tests for programs (requires root)
- Example programs demonstrating key features
- Simple kprobe example
- Execve tracer example
- Map operations example
- Clojure 1.12.0
- tools.logging 1.3.0
- Java 25+ (for Panama FFI)
- Zero external dependencies!
- Linux kernel 4.14+ (5.8+ recommended)
- CAP_BPF and CAP_PERFMON capabilities (or root)
- BPF filesystem mounted
- Tracefs mounted (for kprobes/tracepoints)
- Ring buffer memory-mapping not yet implemented (basic polling only)
- Perf event buffers not fully implemented
- ELF object file parsing not implemented
- BTF support not yet available
- XDP, TC, cgroup, LSM attachments not yet implemented
Note: Many of these limitations have been addressed in later releases. See the
full changelog for current capabilities.
See README.md for complete roadmap of planned features.