Remove kprobe legacy logic once upstream accepts it about libbpfgo HOT 6 CLOSED

Commit got merged in for-next (bpf-next):

commit 467b3225553a (HEAD -> rafaeldtinoco, origin/master, origin/for-next, origin/HEAD)
Author: Rafael David Tinoco <[email protected]>
Date:   Sun Sep 12 03:48:44 2021

    libbpf: Introduce legacy kprobe events support

    Allow kprobe tracepoint events creation through legacy interface, as the
    kprobe dynamic PMUs support, used by default, was only created in v4.17.

    Store legacy kprobe name in struct bpf_perf_link, instead of creating
    a new "subclass" off of bpf_perf_link. This is ok as it's just two new
    fields, which are also going to be reused for legacy uprobe support in
    follow up patches.

    Signed-off-by: Rafael David Tinoco <[email protected]>
    Signed-off-by: Andrii Nakryiko <[email protected]>
    Link: https://lore.kernel.org/bpf/[email protected]

It will get into bpf-next and, eventually, into libbpf (github). We will be able to get rid of legacy kprobe functions.

from libbpfgo.

I think we should wait with that until libbpf 0.6.0 (which should include the patch) will be out

from libbpfgo.

Latest proposal at LORE thread.

from libbpfgo.

Latest proposal at:

https://lore.kernel.org/bpf/[email protected]/

already to be applied on top of the:

[PATCH v3 bpf-next 00/14] BPF perf link and user-provided bpf_cookie

patch set from Andrii. It will need to wait until that patch set is merged. It correctly replaces libbpfgo legacy kprobe implementation embedded at libbpfgo.go source code (for current libbpf upstream branch).

from libbpfgo.

Alright, the legacy kprobe logic just got merged into libbpf:

libbpf/libbpf@749b394

and into bpf-next tree. Andrii has already refactored it to support legacy uprobes as well as some fixes.

We're ready for the legacy kprobe specific functions removal in libbpfgo.

from libbpfgo.

@rafaeldtinoco I think we can now remove those functions, can't we?

from libbpfgo.