Repository navigation
[CI/tigron]: investigate file descriptor leak detection as a testing feature #4029
Description
What is the problem you're trying to solve
Probably leverage lsof -nP -p X (or implement it in go)
Describe the solution you'd like
Automatically fail a test if the test is leaking file descriptors.
Ideally, fail a test if the tested binary is leaking.
Additional context
Note: evaluate #4013 as well.
Activity
[-]CI/tigron: investigate file descriptor leak detection as a testing feature[/-][+][CI/tigron]: investigate file descriptor leak detection as a testing feature[/+]apostasie commentedon Mar 20, 2025
@fahedouch can you tentatively mark this for milestone 2.x.x?
apostasie commentedon Mar 30, 2025
Possibly investigate using: https://github.com/u-root/u-root/blob/main/pkg/strace
@AkihiroSuda any idea how to best approach the problem of finding file leaks overall in tested binaries?
I am currently thinking ptrace-ing
cmd.Exec(some golang equivalent ofstrace -e trace=open,openat,close -f -p XXX)?Wondering if gomodjail could be made a bit more generic to allow for usecases like this?
Or if we could have a standalone library for that used by gomodjail?
eg: having something like
stracelib.Trace(*exec.Cmd, callback func(ProcessSomething, SyscallSomething)...)This is not trivial stuff.
apostasie commentedon May 3, 2025
@AkihiroSuda not happening before 05/06 => v2.2