Null bytes in process binary names

[willfindlay]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

We noticed some null bytes in process binary names where there shouldn't be any. Reproducible by letting Tetragon run for a while under a simple test workload and watching the metrics. You end up with binary names like the following when viewing the mtrics in vim:

tetragon_events_total{binary="^@^@^@^@^@^@^@^@^@^@^@^@^@",namespace="",pod="",type="PROCESS_EXEC"} 1
tetragon_events_total{binary="^@^@^@^@^@^@^@^@^@^@^@^@^@",namespace="",pod="",type="PROCESS_EXIT"} 1
tetragon_events_total{binary="^@^@^@^@^@^@^@^@^@^@^@^@^@^@",namespace="",pod="",type="PROCESS_EXIT"} 1

Tetragon Version

Main at tag eb69bdc

Kernel Version

Linux 5.15.0-69-generic x86_64

Kubernetes Version

No response

Bugtool

No response

Relevant log output

No response

Anything else?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct