The target_btf_id can help us understand which kernel function is
linked by a tracing prog. The target_btf_id and target_obj_id have
already been exposed to userspace, so we just need to show them.
For some other link types like perf_event and kprobe_multi, it is not
easy to find which functions are attached either. We may support
->fill_link_info for them in the future.
Yafang Shao (2):
bpf: Show target_{obj,btf}_id in tracing link fdinfo
bpftool: Show target_{obj,btf}_id in tracing link info
kernel/bpf/syscall.c | 12 ++++++++++--
tools/bpf/bpftool/link.c | 4 ++++
2 files changed, 14 insertions(+), 2 deletions(-)
--
1.8.3.1
