From: Song Liu <songliubraving@fb.com>
To: Alexei Starovoitov <ast@fb.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
David Miller <davem@davemloft.net>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"x86@kernel.org" <x86@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH v3 bpf-next 16/18] libbpf: Add support for attaching BPF programs to other BPF programs
Date: Fri, 8 Nov 2019 19:14:17 +0000 [thread overview]
Message-ID: <484B1B7E-8B72-4BF1-A8DB-ECEEAC69E269@fb.com> (raw)
In-Reply-To: <624d217e-ac6f-f69b-855d-b3b533ed5104@fb.com>
> On Nov 8, 2019, at 11:13 AM, Alexei Starovoitov <ast@fb.com> wrote:
>
> On 11/8/19 10:57 AM, Song Liu wrote:
>>
>>
>>> On Nov 7, 2019, at 10:40 PM, Alexei Starovoitov <ast@kernel.org> wrote:
>>>
>>> Extend libbpf api to pass attach_prog_fd into bpf_object__open.
>>>
>>> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
>>> ---
>>
>> [...]
>>
>>> +static int libbpf_find_prog_btf_id(const char *name, __u32 attach_prog_fd)
>>> +{
>>> + struct bpf_prog_info_linear *info_linear;
>>> + struct bpf_prog_info *info;
>>> + struct btf *btf = NULL;
>>> + int err = -EINVAL;
>>> +
>>> + info_linear = bpf_program__get_prog_info_linear(attach_prog_fd, 0);
>>> + if (IS_ERR_OR_NULL(info_linear)) {
>>> + pr_warn("failed get_prog_info_linear for FD %d\n",
>>> + attach_prog_fd);
>>> + return -EINVAL;
>>> + }
>>> + info = &info_linear->info;
>>> + if (!info->btf_id) {
>>> + pr_warn("The target program doesn't have BTF\n");
>>> + goto out;
>>> + }
>>> + if (btf__get_from_id(info->btf_id, &btf)) {
>>> + pr_warn("Failed to get BTF of the program\n");
>>> + goto out;
>>> + }
>>> + err = btf__find_by_name_kind(btf, name, BTF_KIND_FUNC);
>>> + btf__free(btf);
>>> + if (err <= 0) {
>>> + pr_warn("%s is not found in prog's BTF\n", name);
>>> + goto out;
>> ^^^ This goto doesn't really do much.
>
> yeah. it does look a bit weird.
> I wanted to keep uniform error handling, but can remove it
> if you insist.
I think it is good as-is.
Thanks,
Song
next prev parent reply other threads:[~2019-11-08 19:14 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 6:40 [PATCH v3 bpf-next 00/18] Introduce BPF trampoline Alexei Starovoitov
2019-11-08 6:40 ` [PATCH v3 bpf-next 01/18] bpf: refactor x86 JIT into helpers Alexei Starovoitov
2019-11-08 19:27 ` Andrii Nakryiko
2019-11-08 6:40 ` [PATCH v3 bpf-next 02/18] bpf: Add bpf_arch_text_poke() helper Alexei Starovoitov
2019-11-08 6:56 ` Song Liu
2019-11-08 8:23 ` Björn Töpel
2019-11-08 14:09 ` Alexei Starovoitov
2019-11-08 9:11 ` Peter Zijlstra
2019-11-08 9:36 ` Peter Zijlstra
2019-11-08 13:41 ` Alexei Starovoitov
2019-11-08 19:32 ` Alexei Starovoitov
2019-11-08 21:36 ` Peter Zijlstra
2019-11-08 21:39 ` David Miller
2019-11-11 8:14 ` Peter Zijlstra
2019-11-11 10:21 ` Daniel Borkmann
2019-11-11 16:10 ` Jonathan Corbet
2019-11-08 23:05 ` Alexei Starovoitov
2019-11-10 10:54 ` Thomas Gleixner
2019-11-08 6:40 ` [PATCH v3 bpf-next 03/18] bpf: Introduce BPF trampoline Alexei Starovoitov
2019-11-08 7:04 ` Song Liu
2019-11-08 6:40 ` [PATCH v3 bpf-next 04/18] libbpf: Introduce btf__find_by_name_kind() Alexei Starovoitov
2019-11-08 7:05 ` Song Liu
2019-11-08 19:21 ` Andrii Nakryiko
2019-11-08 6:40 ` [PATCH v3 bpf-next 05/18] libbpf: Add support to attach to fentry/fexit tracing progs Alexei Starovoitov
2019-11-08 7:12 ` Song Liu
2019-11-08 19:44 ` Andrii Nakryiko
2019-11-08 6:40 ` [PATCH v3 bpf-next 06/18] selftest/bpf: Simple test for fentry/fexit Alexei Starovoitov
2019-11-08 6:40 ` [PATCH v3 bpf-next 07/18] bpf: Add kernel test functions for fentry testing Alexei Starovoitov
2019-11-08 6:40 ` [PATCH v3 bpf-next 08/18] selftests/bpf: Add test for BPF trampoline Alexei Starovoitov
2019-11-08 6:40 ` [PATCH v3 bpf-next 09/18] selftests/bpf: Add fexit tests " Alexei Starovoitov
2019-11-08 6:40 ` [PATCH v3 bpf-next 10/18] selftests/bpf: Add combined fentry/fexit test Alexei Starovoitov
2019-11-08 7:14 ` Song Liu
2019-11-08 6:40 ` [PATCH v3 bpf-next 11/18] selftests/bpf: Add stress test for maximum number of progs Alexei Starovoitov
2019-11-08 7:24 ` Song Liu
2019-11-08 6:40 ` [PATCH v3 bpf-next 12/18] bpf: Reserve space for BPF trampoline in BPF programs Alexei Starovoitov
2019-11-08 7:25 ` Song Liu
2019-11-08 6:40 ` [PATCH v3 bpf-next 13/18] bpf: Fix race in btf_resolve_helper_id() Alexei Starovoitov
2019-11-08 7:32 ` Song Liu
2019-11-08 19:58 ` Andrii Nakryiko
2019-11-08 6:40 ` [PATCH v3 bpf-next 14/18] bpf: Compare BTF types of functions arguments with actual types Alexei Starovoitov
2019-11-08 17:28 ` Song Liu
2019-11-08 17:32 ` Song Liu
2019-11-08 17:57 ` Alexei Starovoitov
2019-11-08 17:59 ` Song Liu
2019-11-08 23:46 ` Andrii Nakryiko
2019-11-08 6:40 ` [PATCH v3 bpf-next 15/18] bpf: Support attaching tracing BPF program to other BPF programs Alexei Starovoitov
2019-11-08 18:49 ` Song Liu
2019-11-08 18:59 ` Alexei Starovoitov
2019-11-08 20:17 ` Toke Høiland-Jørgensen
2019-11-08 21:14 ` Alexei Starovoitov
2019-11-08 21:32 ` Toke Høiland-Jørgensen
2019-11-10 7:17 ` Andrii Nakryiko
2019-11-11 23:04 ` Alexei Starovoitov
2019-11-12 4:38 ` Andrii Nakryiko
2019-11-12 4:47 ` Alexei Starovoitov
2019-11-08 6:40 ` [PATCH v3 bpf-next 16/18] libbpf: Add support for attaching BPF programs " Alexei Starovoitov
2019-11-08 18:57 ` Song Liu
2019-11-08 19:13 ` Alexei Starovoitov
2019-11-08 19:14 ` Song Liu [this message]
2019-11-10 16:56 ` Andrii Nakryiko
2019-11-08 6:40 ` [PATCH v3 bpf-next 17/18] selftests/bpf: Extend test_pkt_access test Alexei Starovoitov
2019-11-08 19:03 ` Song Liu
2019-11-10 16:58 ` Andrii Nakryiko
2019-11-08 6:40 ` [PATCH v3 bpf-next 18/18] selftests/bpf: Add a test for attaching BPF prog to another BPF prog and subprog Alexei Starovoitov
2019-11-08 19:13 ` Song Liu
2019-11-10 17:04 ` Andrii Nakryiko
2019-11-11 23:07 ` 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=484B1B7E-8B72-4BF1-A8DB-ECEEAC69E269@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=ast@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=x86@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).