Scroll to navigation

BPFTOOL-LINK(8) System Manager's Manual BPFTOOL-LINK(8)


bpftool-link - tool for inspection and simple manipulation of eBPF links


bpftool [OPTIONS] link COMMAND

OPTIONS := { { -j | --json } [{ -p | --pretty }] | { -d | --debug } | { -f | --bpffs } | { -n | --nomount } }

COMMANDS := { show | list | pin | help }


bpftool link { show | list } [LINK]
bpftool link pin LINK FILE
bpftool link detach LINK
bpftool link help
LINK := { id LINK_ID | pinned FILE }


Show information about active links. If LINK is specified show information only about given link, otherwise list all links currently active on the system.

Output will start with link ID followed by link type and zero or more named attributes, some of which depend on type of link.

Since Linux 5.8 bpftool is able to discover information about processes that hold open file descriptors (FDs) against BPF links. On such kernels bpftool will automatically emit this information as well.

Pin link LINK as FILE.

Note: FILE must be located in bpffs mount. It must not contain a dot character ('.'), which is reserved for future extensions of bpffs.

Force-detach link LINK. BPF link and its underlying BPF program will stay valid, but they will be detached from the respective BPF hook and BPF link will transition into a defunct state until last open file descriptor for that link is closed.
Print short help message.


Print short help message (similar to bpftool help).
Print bpftool's version number (similar to bpftool version), the number of the libbpf version in use, and optional features that were included when bpftool was compiled. Optional features include linking against LLVM or libbfd to provide the disassembler for JIT-ted programs (bpftool prog dump jited) and usage of BPF skeletons (some features like bpftool prog profile or showing pids associated to BPF objects may rely on it).
Generate JSON output. For commands that cannot produce JSON, this option has no effect.
Generate human-readable JSON output. Implies -j.
Print all logs available, even debug-level information. This includes logs from libbpf as well as from the verifier, when attempting to load programs.

When showing BPF links, show file names of pinned links.
Do not automatically attempt to mount any virtual file system (such as tracefs or BPF virtual file system) when necessary.


# bpftool link show

10: cgroup  prog 25

cgroup_id 614 attach_type egress
pids test_progs(223)

# bpftool --json --pretty link show


"type": "cgroup",
"prog_id": 25,
"cgroup_id": 614,
"attach_type": "egress",
"pids": [{
"pid": 223,
"comm": "test_progs"
} ]

# bpftool link pin id 10 /sys/fs/bpf/link
# ls -l /sys/fs/bpf/

-rw------- 1 root root 0 Apr 23 21:39 link