ior - I/O Riot NG is an experiment with BPF.

Age	Commit message (Collapse)	Author
2026-05-28	close_range: honor last bound and CLOSE_RANGE_CLOEXEC flag	Paul Buetow
	close_range was captured as a single-fd fd_event carrying only first, so the runtime evicted every tracked fd >= first, ignoring the last upper bound and the flags. Bounded calls wrongly dropped still-open higher fds, and CLOSE_RANGE_CLOEXEC (which keeps fds open) was treated as a full close. Reclassify close_range to the two_fd_event kind, mapping fd_a/fd_b/extra to first/last/flags. The runtime now closes only the inclusive [first, last] range (a negative last from ~0U means unbounded) and skips eviction when CLOSE_RANGE_CLOEXEC is set or the syscall fails. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-02-22	Fix event comm attribution and reduce integration log noise	Paul Buetow

2026-02-22	Stabilize close invalid-fd integration test against empty comm	Paul Buetow

2026-02-21	Add negative integration tests for close syscalls	Paul Buetow
	Add three negative scenarios to verify ior captures tracepoints even when close syscalls fail: - close-invalid-fd: close an fd (99999) that was never opened (EBADF) - close-double-close: open a file, close it, close same fd again (EBADF) - close-range-empty: close_range on high fd range with no open fds Task: 348 Amp-Thread-ID: https://ampcode.com/threads/T-019c8190-c9ae-776e-b00d-476207d8c10e Co-authored-by: Amp <amp@ampcode.com>
2026-02-21	more on integration tests	Paul Buetow