diff options
author | 2020-04-28 17:16:06 -0700 | |
---|---|---|
committer | 2020-04-28 17:27:08 -0700 | |
commit | a3b80e1078943dc12553166fb08e258463dec013 (patch) | |
tree | e022212949f8028eacf0c5d3ad77218d7f1a7b1a /include/linux/bpf_types.h | |
parent | bpf: Refactor bpf_link update handling (diff) | |
download | wireguard-linux-a3b80e1078943dc12553166fb08e258463dec013.tar.xz wireguard-linux-a3b80e1078943dc12553166fb08e258463dec013.zip |
bpf: Allocate ID for bpf_link
Generate ID for each bpf_link using IDR, similarly to bpf_map and bpf_prog.
bpf_link creation, initialization, attachment, and exposing to user-space
through FD and ID is a complicated multi-step process, abstract it away
through bpf_link_primer and bpf_link_prime(), bpf_link_settle(), and
bpf_link_cleanup() internal API. They guarantee that until bpf_link is
properly attached, user-space won't be able to access partially-initialized
bpf_link either from FD or ID. All this allows to simplify bpf_link attachment
and error handling code.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Link: https://lore.kernel.org/bpf/20200429001614.1544-3-andriin@fb.com
Diffstat (limited to 'include/linux/bpf_types.h')
0 files changed, 0 insertions, 0 deletions