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

matchBinaries follow-ups #722

Closed
tpapagian opened this issue Feb 23, 2023 · 0 comments · Fixed by #1731
Closed

matchBinaries follow-ups #722

tpapagian opened this issue Feb 23, 2023 · 0 comments · Fixed by #1731

Comments

@tpapagian
Copy link
Member

From 0854a3b:

As a follow-up we can also clear entries from the (shared) names_map
when we remove kprobes. For now we also increase the size of that map to
256 entries. This means that we can define up to 256 unique binary names
among all matchBinaries selectors.

Since the same name may be used by multiple kprobes, we would need reference counting to know when to remove an entry. Or we can just scan everything.

Another limitation is that we only catch binaries that are exec-ed after the policy started.

More details in #686 (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 a pull request may close this issue.

1 participant