Skip to content

Conversation

@javierhonduco
Copy link

To add various useful types including struct syscall_trace_enter
and struct syscall_trace_exit.

See https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/3717

Test Plan

Validated that struct syscall_trace_{enter,exit} is included https://github.com/javierhonduco/vmlinux.h/actions/runs/20752218340

To add various useful types including `struct syscall_trace_enter`
and `struct syscall_trace_exit`.

See https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/3717

Test Plan
=========

Validated that `struct syscall_trace_{enter,exit}` is included https://github.com/javierhonduco/vmlinux.h/actions/runs/20752218340
@javierhonduco
Copy link
Author

Need this as part of fixing javierhonduco/lightswitch#323 (comment)

@danielocfb danielocfb self-requested a review January 6, 2026 17:09
@theihor
Copy link
Contributor

theihor commented Jan 6, 2026

Hi @javierhonduco, thanks for the PR.

The vmlinux.h files with this change will be generated by a CI job. Could you please check that new vmlinux.h fixes your issue and add a commit updating all the vmlinux.h files?

We automated the generation process, but not the "update the files and open a PR" part. Feel free to take that on, if you're interested.

Thank you!

@danielocfb
Copy link
Collaborator

It feels like we should probably make sure to flag outdated headers at the least. I'd assume everything is fully reproducible so we should be able to just diff what we have vs. what we expect. It's what we do in blazesym CI as well, for example. Will see if I can make that work.

@javierhonduco
Copy link
Author

The vmlinux.h files with this change will be generated by a CI job. Could you please check that new vmlinux.h fixes your issue and add a commit updating all the vmlinux.h files?

Was going to add this in another PR but makes sense, will add another commit once the other opened PRs are merged. Thanks for the prompt review and generally improving CI.

@d-e-s-o
Copy link
Contributor

d-e-s-o commented Jan 7, 2026

will add another commit once the other opened PRs are merged

Only #15 should have relevance for you, I believe. So you should be good to go now with the update while the remaining ones are in review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants