diff options
| author |   Alexei Starovoitov <ast@kernel.org> | 2024-10-23 22:15:09 -0700 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2024-10-23 22:15:09 -0700 |
| commit | 39b8ab1519687054769bc07feb97821fc40f56e2 (patch) | |
| tree | dd013a3ee41c6e27cdbe5e415c247a37a359c94b /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | Merge branch 'fix-wmaybe-uninitialized-warnings-errors' (diff) | |
| parent | selftests/bpf: validate generic bpf_object and subskel APIs work together (diff) | |
| download | wireguard-linux-39b8ab1519687054769bc07feb97821fc40f56e2.tar.xz wireguard-linux-39b8ab1519687054769bc07feb97821fc40f56e2.zip | |
Merge branch 'fix-libbpf-s-bpf_object-and-bpf-subskel-interoperability'
Andrii Nakryiko says:
====================
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.
====================
Link: https://lore.kernel.org/r/20241023043908.3834423-1-andrii@kernel.org
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions