From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, andrii@kernel.org,
john.fastabend@gmail.com, bpf@vger.kernel.org,
kernel-team@fb.com
Subject: [PATCH v3 bpf-next 04/17] libbpf: Support for syscall program type
Date: Wed, 5 May 2021 20:44:52 -0700 [thread overview]
Message-ID: <20210506034505.25979-5-alexei.starovoitov@gmail.com> (raw)
In-Reply-To: <20210506034505.25979-1-alexei.starovoitov@gmail.com>
From: Alexei Starovoitov <ast@kernel.org>
Trivial support for syscall program type.
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Andrii Nakryiko <andrii@kernel.org>
---
tools/lib/bpf/libbpf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
index e2a3cf437814..5790166eee9b 100644
--- a/tools/lib/bpf/libbpf.c
+++ b/tools/lib/bpf/libbpf.c
@@ -8958,6 +8958,7 @@ static const struct bpf_sec_def section_defs[] = {
BPF_PROG_SEC("struct_ops", BPF_PROG_TYPE_STRUCT_OPS),
BPF_EAPROG_SEC("sk_lookup/", BPF_PROG_TYPE_SK_LOOKUP,
BPF_SK_LOOKUP),
+ BPF_PROG_SEC("syscall", BPF_PROG_TYPE_SYSCALL),
};
#undef BPF_PROG_SEC_IMPL
--
2.30.2
next prev parent reply other threads:[~2021-05-06 3:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 3:44 [PATCH v3 bpf-next 00/17] bpf: syscall program, FD array, loader program, light skeleton Alexei Starovoitov
2021-05-06 3:44 ` [PATCH v3 bpf-next 01/17] bpf: Introduce bpf_sys_bpf() helper and program type Alexei Starovoitov
2021-05-06 3:44 ` [PATCH v3 bpf-next 02/17] bpf: Introduce bpfptr_t user/kernel pointer Alexei Starovoitov
2021-05-06 3:44 ` [PATCH v3 bpf-next 03/17] bpf: Prepare bpf syscall to be used from kernel and user space Alexei Starovoitov
2021-05-06 3:44 ` Alexei Starovoitov [this message]
2021-05-06 3:44 ` [PATCH v3 bpf-next 05/17] selftests/bpf: Test for syscall program type Alexei Starovoitov
2021-05-06 3:44 ` [PATCH v3 bpf-next 06/17] bpf: Make btf_load command to be bpfptr_t compatible Alexei Starovoitov
2021-05-06 3:44 ` [PATCH v3 bpf-next 07/17] selftests/bpf: Test for btf_load command Alexei Starovoitov
2021-05-06 3:44 ` [PATCH v3 bpf-next 08/17] bpf: Introduce fd_idx Alexei Starovoitov
2021-05-06 3:44 ` [PATCH v3 bpf-next 09/17] libbpf: Support for fd_idx Alexei Starovoitov
2021-05-06 3:44 ` [PATCH v3 bpf-next 10/17] bpf: Add bpf_btf_find_by_name_kind() helper Alexei Starovoitov
2021-05-06 3:44 ` [PATCH v3 bpf-next 11/17] bpf: Add bpf_sys_close() helper Alexei Starovoitov
2021-05-06 3:45 ` [PATCH v3 bpf-next 12/17] libbpf: Change the order of data and text relocations Alexei Starovoitov
2021-05-06 3:45 ` [PATCH v3 bpf-next 13/17] libbpf: Add bpf_object pointer to kernel_supports() Alexei Starovoitov
2021-05-06 3:45 ` [PATCH v3 bpf-next 14/17] libbpf: Generate loader program out of BPF ELF file Alexei Starovoitov
2021-05-06 3:45 ` [PATCH v3 bpf-next 15/17] libbpf: Use fd_array only with gen_loader Alexei Starovoitov
2021-05-06 3:45 ` [PATCH v3 bpf-next 16/17] bpftool: Use syscall/loader program in "prog load" and "gen skeleton" command Alexei Starovoitov
2021-05-06 3:45 ` [PATCH v3 bpf-next 17/17] selftests/bpf: Convert few tests to light skeleton Alexei Starovoitov
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=20210506034505.25979-5-alexei.starovoitov@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@fb.com \
/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).