Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

current process in sched_process_fork not child #282

Open
banditopazzo opened this issue Apr 30, 2024 · 0 comments
Open

current process in sched_process_fork not child #282

banditopazzo opened this issue Apr 30, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@banditopazzo
Copy link
Member

Currently we are using the tracepoint sched_process_fork to intercept fork events.

The output Fork pulsar event has the ppid in it's payload and the metadata in the Header struct (example: pid, image, ecc) belongs to the child process.

The problem is that in the BPF probe attached to sched_process_fork the bpf_get_current_xxx functions return parent data and we are using their output to fill child structures.

To have the event semantically correct, we should make the event relative to the parent process but this is not possible because we have some process details resolved in userspace, for example the image.

Probably the best solution right now is to leave it as child event, maybe renaming it to something else (example: ProcessCreated), and fix the probe to get all data from child struct task_struct.

@krsh krsh added the enhancement New feature or request label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants