Skip to content

Conversation

@secDre4mer
Copy link
Contributor

Add support for more link inspection types, e.g. to query a uprobe's symbol.

@secDre4mer secDre4mer force-pushed the feat/add-link-info-types branch 2 times, most recently from 26a871d to 9b0dcdd Compare November 7, 2025 08:59
@secDre4mer secDre4mer marked this pull request as ready for review November 7, 2025 08:59
@secDre4mer secDre4mer requested review from a team and mmat11 as code owners November 7, 2025 08:59
Copy link
Contributor

@mmat11 mmat11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks mostly good to me, left a few comments; can this be split in multiple commits?

if umi.offsets == nil {
return nil, fmt.Errorf("no offsets available")
}
ex, err := OpenExecutable(umi.path)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm I wonder if this is safe to do; should we just return addresses like for kprobeMulti?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure, that's why there are the different Offsets and Symbols functions. Offsets returns the raw offsets, and only Symbols tries to resolve them.

@secDre4mer
Copy link
Contributor Author

looks mostly good to me, left a few comments; can this be split in multiple commits?

Sure, I'll try. Any ideas on how the commits should be structured? E.g. one focused on uprobe, one focused on tracepoint, ...?

@mmat11
Copy link
Contributor

mmat11 commented Nov 10, 2025

looks mostly good to me, left a few comments; can this be split in multiple commits?

Sure, I'll try. Any ideas on how the commits should be structured? E.g. one focused on uprobe, one focused on tracepoint, ...?

I guess you could split code generation and the different link types in different commits

@github-actions github-actions bot added the breaking-change Changes exported API label Nov 10, 2025
@secDre4mer secDre4mer force-pushed the feat/add-link-info-types branch from 9b0dcdd to d0b8794 Compare November 10, 2025 08:16
The netfilter options / info required / contained protocol family
and hook, with little information for the user what
values were expected.
Add explicit types with constants to clarify what values are
supported.

Signed-off-by: Max Altgelt <[email protected]>
@secDre4mer secDre4mer force-pushed the feat/add-link-info-types branch from d0b8794 to 5f0a645 Compare November 10, 2025 08:16
@secDre4mer
Copy link
Contributor Author

Split is done.

@secDre4mer secDre4mer requested a review from mmat11 November 11, 2025 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking-change Changes exported API

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants