You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When attaching uprobe, it is necessary to verify if the PID matches the options in the command line.(--pids, --comm), if not skip attaching.
Describe the solution you'd like
code in agent/uprobe/manager.go#handleSchedExecEvent():
funchandleSchedExecEvent(event*bpf.AgentProcessExecEvent) {
// check pid here
}
Describe alternatives you've considered
None
Additional context
None
The text was updated successfully, but these errors were encountered:
Does AgentProcessExecEvent.pid match the PIDs from the command? I noticed that event.pid differs with each event. Is this expected behavior?
Whenever a new process starts, an AgentProcessExecEvent is triggered. This is expected behavior. We need to check whether the pid or command name in the AgentProcessExecEvent matches the one specified in the command line. (Or we can just validate the comm, because I believe no one can predict the pid.)
Is your feature request related to a problem? Please describe.
When attaching uprobe, it is necessary to verify if the PID matches the options in the command line.(
--pids
,--comm
), if not skip attaching.Describe the solution you'd like
code in agent/uprobe/manager.go#handleSchedExecEvent():
Describe alternatives you've considered
None
Additional context
None
The text was updated successfully, but these errors were encountered: