fix: BPF_PROG_TYPE issue for android #275
Draft
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
pomhg
changed the title
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.
Background
pname is useful for dae running on android, e.g. pname(netd) -> must_direct. (
netdis the networkmanager for android)dae pname not working on android, coz the bpf prog type name is different in libbpf_android.
Error 1
FATA[0002] Attach(group: (GroupSock(tproxy_wan_cg_sock_create)#27: create link: operation not permittedError 2
FATA[0000] load eBPF objects: field TproxyWanCgConnect4: cannot load program tproxy_wan_cg_connect4: program type is unspecifiedRefs.
AOSP Extending the Kernel with eBPF
Loader.cpp main branch source
Loader.cpp android13-qpr3-release branch source
Checklist
Full Changelogs
Issue Reference
Closes #[issue number]
Test Result