Merge branch 'bpf-cleanup-btf-raw-tp'
authorDaniel Borkmann <daniel@iogearbox.net>
Thu, 31 Oct 2019 14:16:59 +0000 (15:16 +0100)
committerDaniel Borkmann <daniel@iogearbox.net>
Thu, 31 Oct 2019 14:17:14 +0000 (15:17 +0100)
commit06087114606c416892bd67c5fde9f0d498afb287
tree6193b759236e868ec2bdc75f9107a43123dbca13
parentaf91acbc62999d62e2ca1e80f660d20561ca55d3
parent12a8654b2e5aab37b22c9608d008f9f0565862c0
Merge branch 'bpf-cleanup-btf-raw-tp'

Alexei Starovoitov says:

====================
v1->v2: addressed Andrii's feedback

When BTF-enabled raw_tp were introduced the plan was to follow up
with BTF-enabled kprobe and kretprobe reusing PROG_RAW_TRACEPOINT
and PROG_KPROBE types. But k[ret]probe expect pt_regs while
BTF-enabled program ctx will be the same as raw_tp.
kretprobe is indistinguishable from kprobe while BTF-enabled
kretprobe will have access to retval while kprobe will not.
Hence PROG_KPROBE type is not reusable and reusing
PROG_RAW_TRACEPOINT no longer fits well.
Hence introduce 'umbrella' prog type BPF_PROG_TYPE_TRACING
that will cover different BTF-enabled tracing attach points.
The changes make libbpf side cleaner as well.
check_attach_btf_id() is cleaner too.
====================

Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>