-
Notifications
You must be signed in to change notification settings - Fork 20
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
Rewrite in Rust #199
Merged
Merged
Rewrite in Rust #199
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vadorovsky
force-pushed
the
aya-ebpf-3
branch
3 times, most recently
from
May 4, 2022 18:02
50e07a9
to
4e7662d
Compare
vadorovsky
force-pushed
the
aya-ebpf-3
branch
3 times, most recently
from
May 13, 2022 20:53
cafb7cc
to
b135f44
Compare
vadorovsky
force-pushed
the
aya-ebpf-3
branch
4 times, most recently
from
May 14, 2022 21:27
e76e686
to
fd05682
Compare
vadorovsky
force-pushed
the
aya-ebpf-3
branch
2 times, most recently
from
May 14, 2022 22:01
dc682df
to
3c54031
Compare
Finally, we are getting rid of C and libbpf here. This PR replaces all the eBPF programs with Rust programs written in Aya. The part of this PR is also: * fetching recent, relevant changes in aya-template * detecting new processes only with tracepoints, the task LSM program was removed The only omitted program is file_open, which is going to be added in a follow up change. Fixes: lockc-project#49 Fixes: lockc-project#137 Fixes: lockc-project#138 Signed-off-by: Michal Rostecki <[email protected]>
vadorovsky
added a commit
to vadorovsky/lockc
that referenced
this pull request
May 15, 2022
After lockc-project#199 we don't have to use libbpf anymore. Since building stuff with Rust locally is easy (and only rustup is required), it's also time to get rid of dapper. Signed-off-by: Michal Rostecki <[email protected]>
vadorovsky
added a commit
to vadorovsky/lockc
that referenced
this pull request
May 15, 2022
After lockc-project#199 we don't have to use libbpf anymore. Since building stuff with Rust locally is easy (and only rustup is required), it's also time to get rid of dapper. Signed-off-by: Michal Rostecki <[email protected]>
vadorovsky
added a commit
to vadorovsky/lockc
that referenced
this pull request
May 15, 2022
After lockc-project#199 we don't have to use libbpf anymore. Since building stuff with Rust locally is easy (and only rustup is required), it's also time to get rid of dapper. Signed-off-by: Michal Rostecki <[email protected]>
vadorovsky
added a commit
to vadorovsky/lockc
that referenced
this pull request
May 15, 2022
After lockc-project#199 we don't have to use libbpf anymore. Since building stuff with Rust locally is easy (and only rustup is required), it's also time to get rid of dapper. Signed-off-by: Michal Rostecki <[email protected]>
vadorovsky
added a commit
to vadorovsky/lockc
that referenced
this pull request
May 15, 2022
After lockc-project#199 we don't have to use libbpf anymore. Since building stuff with Rust locally is easy (and only rustup is required), it's also time to get rid of dapper. Signed-off-by: Michal Rostecki <[email protected]>
vadorovsky
added a commit
to vadorovsky/lockc
that referenced
this pull request
May 15, 2022
After lockc-project#199 we don't have to use libbpf anymore. Since building stuff with Rust locally is easy (and only rustup is required), it's also time to get rid of dapper. Signed-off-by: Michal Rostecki <[email protected]>
vadorovsky
added a commit
to vadorovsky/lockc
that referenced
this pull request
May 15, 2022
After lockc-project#199 we don't have to use libbpf anymore. Since building stuff with Rust locally is easy (and only rustup is required), it's also time to get rid of dapper. Signed-off-by: Michal Rostecki <[email protected]>
vadorovsky
added a commit
to vadorovsky/lockc
that referenced
this pull request
May 16, 2022
After lockc-project#199 we don't have to use libbpf anymore. Since building stuff with Rust locally is easy (and only rustup is required), it's also time to get rid of dapper. Signed-off-by: Michal Rostecki <[email protected]>
vadorovsky
added a commit
to lockc-project/lockc-project.github.io
that referenced
this pull request
May 16, 2022
After merging lockc-project/lockc#199 we no longer depend on llvm, libbpf and any C-related technology, cargo and rust are enough. Because of that simplification, it's also time to remove dapper. Signed-off-by: Michal Rostecki <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Finally, we are getting rid of C and libbpf here. This PR replaces
all the eBPF programs with Rust programs written in Aya.
The part of this PR is also:
was removed
The only omitted program is file_open, which is going to be added in a
follow up change.
Fixes: #49
Fixes: #137
Fixes: #138
Signed-off-by: Michal Rostecki [email protected]