From: Yonghong Song <yhs@fb.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
Networking <netdev@vger.kernel.org>,
Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>, Hao Luo <haoluo@google.com>
Subject: Re: [PATCH v2 bpf-next 5/7] bpf: support BPF ksym variables in kernel modules
Date: Mon, 11 Jan 2021 17:25:17 -0800 [thread overview]
Message-ID: <bf8a6fb9-40fd-7037-dcfd-24595b691c8f@fb.com> (raw)
In-Reply-To: <CAEf4BzYtBXr_8HnQEcHn9nQfmMzq_wfdF3jFWzFtOpSF1Uwfug@mail.gmail.com>
On 1/11/21 1:29 PM, Andrii Nakryiko wrote:
> On Sun, Jan 10, 2021 at 8:13 PM Yonghong Song <yhs@fb.com> wrote:
>>
>>
>>
>> On 1/8/21 2:09 PM, Andrii Nakryiko wrote:
>>> Add support for directly accessing kernel module variables from BPF programs
>>> using special ldimm64 instructions. This functionality builds upon vmlinux
>>> ksym support, but extends ldimm64 with src_reg=BPF_PSEUDO_BTF_ID to allow
>>> specifying kernel module BTF's FD in insn[1].imm field.
>>>
>>> During BPF program load time, verifier will resolve FD to BTF object and will
>>> take reference on BTF object itself and, for module BTFs, corresponding module
>>> as well, to make sure it won't be unloaded from under running BPF program. The
>>> mechanism used is similar to how bpf_prog keeps track of used bpf_maps.
>>>
>>> One interesting change is also in how per-CPU variable is determined. The
>>> logic is to find .data..percpu data section in provided BTF, but both vmlinux
>>> and module each have their own .data..percpu entries in BTF. So for module's
>>> case, the search for DATASEC record needs to look at only module's added BTF
>>> types. This is implemented with custom search function.
>>>
>>> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
>>
>> Ack with a minor nit below.
>>
>> Acked-by: Yonghong Song <yhs@fb.com>
>>
>>> ---
>>> include/linux/bpf.h | 10 +++
>>> include/linux/bpf_verifier.h | 3 +
>>> include/linux/btf.h | 3 +
>>> kernel/bpf/btf.c | 31 +++++++-
>>> kernel/bpf/core.c | 23 ++++++
>>> kernel/bpf/verifier.c | 149 ++++++++++++++++++++++++++++-------
>>> 6 files changed, 189 insertions(+), 30 deletions(-)
>>>
>> [...]
>>> /* replace pseudo btf_id with kernel symbol address */
>>> static int check_pseudo_btf_id(struct bpf_verifier_env *env,
>>> struct bpf_insn *insn,
>
> [...]
>
>>> } else {
>>> aux->btf_var.reg_type = PTR_TO_BTF_ID;
>>> - aux->btf_var.btf = btf_vmlinux;
>>> + aux->btf_var.btf = btf;
>>> aux->btf_var.btf_id = type;
>>> }
>>> +
>>> + /* check whether we recorded this BTF (and maybe module) already */
>>> + for (i = 0; i < env->used_btf_cnt; i++) {
>>> + if (env->used_btfs[i].btf == btf) {
>>> + btf_put(btf);
>>> + return 0;
>>
>> An alternative way is to change the above code as
>> err = 0;
>> goto err_put;
>
> I didn't do it, because it's not really an error case, which err_put
> implies. If in the future we'll have some more clean up to do, it
> might make sense, I suppose.
You can change label err_put to btf_put, so this way, btf_put() will
only show up in one place. But I won't insist on this.
>
>>
>>> + }
>>> + }
>>> +
>>> + if (env->used_btf_cnt >= MAX_USED_BTFS) {
>>> + err = -E2BIG;
>>> + goto err_put;
>>> + }
>>> +
>>> + btf_mod = &env->used_btfs[env->used_btf_cnt];
>>> + btf_mod->btf = btf;
>>> + btf_mod->module = NULL;
>>> +
>>> + /* if we reference variables from kernel module, bump its refcount */
>>> + if (btf_is_module(btf)) {
>>> + btf_mod->module = btf_try_get_module(btf);
>>> + if (!btf_mod->module) {
>>> + err = -ENXIO;
>>> + goto err_put;
>>> + }
>>> + }
>>> +
>>> + env->used_btf_cnt++;
>>> +
>>> return 0;
>>> +err_put:
>>> + btf_put(btf);
>>> + return err;
>>> }
>>>
>> [...]
next prev parent reply other threads:[~2021-01-12 1:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 22:09 [PATCH v2 bpf-next 0/7] Support kernel module ksym variables Andrii Nakryiko
2021-01-08 22:09 ` [PATCH v2 bpf-next 1/7] bpf: add bpf_patch_call_args prototype to include/linux/bpf.h Andrii Nakryiko
2021-01-11 4:02 ` Yonghong Song
2021-01-08 22:09 ` [PATCH v2 bpf-next 2/7] bpf: avoid warning when re-casting __bpf_call_base into __bpf_call_base_args Andrii Nakryiko
2021-01-11 4:03 ` Yonghong Song
2021-01-08 22:09 ` [PATCH v2 bpf-next 3/7] bpf: declare __bpf_free_used_maps() unconditionally Andrii Nakryiko
2021-01-11 4:03 ` Yonghong Song
2021-01-08 22:09 ` [PATCH v2 bpf-next 4/7] selftests/bpf: sync RCU before unloading bpf_testmod Andrii Nakryiko
2021-01-11 4:05 ` Yonghong Song
2021-01-11 18:59 ` Hao Luo
2021-01-08 22:09 ` [PATCH v2 bpf-next 5/7] bpf: support BPF ksym variables in kernel modules Andrii Nakryiko
2021-01-11 4:13 ` Yonghong Song
2021-01-11 21:29 ` Andrii Nakryiko
2021-01-12 1:25 ` Yonghong Song [this message]
2021-01-11 18:59 ` Hao Luo
2021-01-11 21:31 ` Andrii Nakryiko
2021-01-08 22:09 ` [PATCH v2 bpf-next 6/7] libbpf: support kernel module ksym externs Andrii Nakryiko
2021-01-11 4:15 ` Yonghong Song
2021-01-11 21:37 ` Andrii Nakryiko
2021-01-12 1:34 ` Yonghong Song
2021-01-12 6:45 ` Andrii Nakryiko
2021-01-11 19:00 ` Hao Luo
2021-01-11 21:39 ` Andrii Nakryiko
2021-01-08 22:09 ` [PATCH v2 bpf-next 7/7] selftests/bpf: test " Andrii Nakryiko
2021-01-11 4:18 ` Yonghong Song
2021-01-11 21:40 ` Andrii Nakryiko
2021-01-11 19:00 ` Hao Luo
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=bf8a6fb9-40fd-7037-dcfd-24595b691c8f@fb.com \
--to=yhs@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--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).