From: Martin KaFai Lau <kafai@fb.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>, <kernel-team@fb.com>
Subject: [PATCH v3 net-next 0/8] Introduce bpf ID
Date: Mon, 5 Jun 2017 12:15:45 -0700 [thread overview]
Message-ID: <cover.1496686606.git.kafai@fb.com> (raw)
This patch series:
1) Introduce ID for both bpf_prog and bpf_map.
2) Add bpf commands to iterate the prog IDs and map
IDs of the system.
3) Add bpf commands to get a prog/map fd from an ID
4) Add bpf command to get prog/map info from a fd.
The prog/map info is a jump start in this patchset
and it is not meant to be a complete list. They can
be extended in the future patches.
v3:
- I suspect v2 may not have applied cleanly.
In particular, patch 1 has conflict with a recent
change in struct bpf_prog_aux introduced at a similar time frame:
8726679a0fa3 ("bpf: teach verifier to track stack depth")
v3 should have fixed it.
v2:
Compiler warning fixes:
- Remove lockdep_is_held() usage. Add comment
to explain the lock situation instead.
- Add static for idr related variables
- Add __user to the uattr param in bpf_prog_get_info_by_fd()
and bpf_map_get_info_by_fd().
Martin KaFai Lau (8):
bpf: Introduce bpf_prog ID
bpf: Introduce bpf_map ID
bpf: Add BPF_(PROG|MAP)_GET_NEXT_ID command
bpf: Add BPF_PROG_GET_FD_BY_ID
bpf: Add BPF_MAP_GET_FD_BY_ID
bpf: Add jited_len to struct bpf_prog
bpf: Add BPF_OBJ_GET_INFO_BY_FD
bpf: Test for bpf ID
arch/arm64/net/bpf_jit_comp.c | 1 +
arch/powerpc/net/bpf_jit_comp64.c | 1 +
arch/s390/net/bpf_jit_comp.c | 1 +
arch/sparc/net/bpf_jit_comp_64.c | 1 +
arch/x86/net/bpf_jit_comp.c | 1 +
include/linux/bpf.h | 2 +
include/linux/filter.h | 3 +-
include/uapi/linux/bpf.h | 41 +++
kernel/bpf/syscall.c | 433 ++++++++++++++++++++++++++++--
tools/include/uapi/linux/bpf.h | 41 +++
tools/lib/bpf/bpf.c | 68 +++++
tools/lib/bpf/bpf.h | 5 +
tools/testing/selftests/bpf/Makefile | 2 +-
tools/testing/selftests/bpf/test_obj_id.c | 35 +++
tools/testing/selftests/bpf/test_progs.c | 191 +++++++++++++
15 files changed, 798 insertions(+), 28 deletions(-)
create mode 100644 tools/testing/selftests/bpf/test_obj_id.c
--
2.9.3
next reply other threads:[~2017-06-05 19:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 19:15 Martin KaFai Lau [this message]
2017-06-05 19:15 ` [PATCH v3 net-next 1/8] bpf: Introduce bpf_prog ID Martin KaFai Lau
2017-06-05 19:15 ` [PATCH v3 net-next 2/8] bpf: Introduce bpf_map ID Martin KaFai Lau
2017-06-05 19:15 ` [PATCH v3 net-next 3/8] bpf: Add BPF_(PROG|MAP)_GET_NEXT_ID command Martin KaFai Lau
2017-06-05 19:15 ` [PATCH v3 net-next 4/8] bpf: Add BPF_PROG_GET_FD_BY_ID Martin KaFai Lau
2017-06-05 19:15 ` [PATCH v3 net-next 5/8] bpf: Add BPF_MAP_GET_FD_BY_ID Martin KaFai Lau
2017-06-05 19:15 ` [PATCH v3 net-next 6/8] bpf: Add jited_len to struct bpf_prog Martin KaFai Lau
2017-06-05 19:15 ` [PATCH v3 net-next 7/8] bpf: Add BPF_OBJ_GET_INFO_BY_FD Martin KaFai Lau
2017-06-05 19:15 ` [PATCH v3 net-next 8/8] bpf: Test for bpf ID Martin KaFai Lau
2017-06-06 19:41 ` [PATCH v3 net-next 0/8] Introduce " David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1496686606.git.kafai@fb.com \
--to=kafai@fb.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).