Fix libbpf's bpf_object and BPF subskel interoperability
Status from this message: This series was applied to bpf/bpf-next.git (master)
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 All 3 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | selftests/bpf: fix test_spin_lock_fail.c's global vars usagetools/ | +2 | 0 replies | Applied |
| 2/3 | libbpf: move global data mmap()'ing into bpf_object__load()tools/ | +40 | 2 replies | Applied |
| 3/3 | selftests/bpf: validate generic bpf_object and subskel APIs work togethertools/ | +75 | 0 replies | Applied |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH bpf-next 0/3] Fix libbpf's bpf_object and BPF subskel interoperability
Fix libbpf's global data map mmap()'ing logic to make BPF objects loaded through generic bpf_object__load() API interoperable with BPF subskeleton instantiated from such BPF object. The issue is in re-mmap()'ing of global data maps after BPF object is loaded into kernel, which is currently done in BPF skeleton-specific code, and should instead be done in generic and common bpf_object_load() logic.
See patch #2 for the fix, patch #3 for the selftests. Patch #1 is preliminary fix for existing spin_lock selftests which currently works by accident.
Andrii Nakryiko (3):
selftests/bpf: fix test_spin_lock_fail.c's global vars usage
libbpf: move global data mmap()'ing into bpf_object__load() selftests/bpf: validate generic bpf_object and subskel APIs work
together
tools/lib/bpf/libbpf.c | 83 +++++++++---------- .../selftests/bpf/prog_tests/subskeleton.c | 76 ++++++++++++++++- .../selftests/bpf/progs/test_spin_lock_fail.c | 4 +- 3 files changed, 117 insertions(+), 46 deletions(-)
Signature · 1 line
2.43.5