-
Notifications
You must be signed in to change notification settings - Fork 5
Multi-split BTF fixes and test #6243
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
base: bpf-next_base
Are you sure you want to change the base?
Multi-split BTF fixes and test #6243
Conversation
|
Upstream branch: 54c134f |
b8a9697 to
0ff1d70
Compare
|
Upstream branch: e2e668b |
a51f45f to
83e49fc
Compare
0ff1d70 to
75ba762
Compare
|
Upstream branch: d28c0e4 |
83e49fc to
55d7a3c
Compare
75ba762 to
385f65b
Compare
|
Upstream branch: 5701d5a |
55d7a3c to
0c85a72
Compare
385f65b to
9a71dd4
Compare
When creating multi-split BTF we correctly set the start string offset to be the size of the base string section plus the base BTF start string offset; the latter is needed for multi-split BTF since the offset is non-zero there. Unfortunately the BTF parsing case needed that logic and it was missed. Fixes: 4e29128 ("libbpf/btf: Fix string handling to support multi-split BTF") Signed-off-by: Alan Maguire <[email protected]>
Write raw BTF to files, parse it and compare to original; this allows us to test parsing of (multi-)split BTF code. Signed-off-by: Alan Maguire <[email protected]>
|
Upstream branch: ab01bfa |
0c85a72 to
51ac981
Compare
Pull request for series with
subject: Multi-split BTF fixes and test
version: 3
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=1016942