-
Notifications
You must be signed in to change notification settings - Fork 149
Multi-split BTF fixes and test #10134
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
Conversation
|
Upstream branch: 54c134f |
AI reviewed your patch. Please fix the bug or email reply why it's not a bug. In-Reply-To-Subject: |
|
Forwarding comment 3458953736 via email |
4481a85 to
5125528
Compare
|
Upstream branch: e2e668b |
9da54f1 to
f34237f
Compare
5125528 to
1e2d874
Compare
|
Upstream branch: 5701d5a |
f34237f to
408375d
Compare
1e2d874 to
c942b08
Compare
|
Upstream branch: ab01bfa |
408375d to
9aeb14c
Compare
c942b08 to
792b8cb
Compare
|
Upstream branch: e6e10c5 |
9aeb14c to
b1ba4b4
Compare
792b8cb to
19d946b
Compare
|
Upstream branch: 5dae745 |
b1ba4b4 to
96440ff
Compare
19d946b to
2ee124c
Compare
|
Upstream branch: 11369e6 |
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]>
96440ff to
4a4fbc2
Compare
|
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=1016942 expired. Closing PR. |
Pull request for series with
subject: Multi-split BTF fixes and test
version: 3
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=1016942