From: Martin KaFai Lau <martin.lau@linux.dev>
To: Kui-Feng Lee <sinquersw@gmail.com>, thinker.li@gmail.com
Cc: kuifeng@meta.com, bpf@vger.kernel.org, ast@kernel.org,
song@kernel.org, kernel-team@meta.com, andrii@kernel.org,
drosen@google.com
Subject: Re: [PATCH bpf-next v11 07/13] bpf: pass attached BTF to the bpf_struct_ops subsystem
Date: Mon, 27 Nov 2023 14:08:06 -0800 [thread overview]
Message-ID: <4880ee9f-780c-4b7c-a292-578212da8273@linux.dev> (raw)
In-Reply-To: <180568df-308f-4bc5-8a54-a9f224123429@gmail.com>
On 11/22/23 2:33 PM, Kui-Feng Lee wrote:
>>> diff --git a/kernel/bpf/bpf_struct_ops.c b/kernel/bpf/bpf_struct_ops.c
>>> index 4ba6181ed1c4..2fb1b21f989a 100644
>>> --- a/kernel/bpf/bpf_struct_ops.c
>>> +++ b/kernel/bpf/bpf_struct_ops.c
>>> @@ -635,6 +635,7 @@ static void __bpf_struct_ops_map_free(struct bpf_map *map)
>>> bpf_jit_uncharge_modmem(PAGE_SIZE);
>>> }
>>> bpf_map_area_free(st_map->uvalue);
>>> + btf_put(st_map->btf);
>>> bpf_map_area_free(st_map);
>>> }
>>> @@ -675,15 +676,30 @@ static struct bpf_map *bpf_struct_ops_map_alloc(union
>>> bpf_attr *attr)
>>> struct bpf_struct_ops_map *st_map;
>>> const struct btf_type *t, *vt;
>>> struct bpf_map *map;
>>> + struct btf *btf;
>>> int ret;
>>> - st_ops_desc = bpf_struct_ops_find_value(btf_vmlinux,
>>> attr->btf_vmlinux_value_type_id);
>>> - if (!st_ops_desc)
>>> - return ERR_PTR(-ENOTSUPP);
>>> + if (attr->value_type_btf_obj_fd) {
>>> + /* The map holds btf for its whole life time. */
>>> + btf = btf_get_by_fd(attr->value_type_btf_obj_fd);
>>> + if (IS_ERR(btf))
>>> + return ERR_PTR(PTR_ERR(btf));
>>> + } else {
>>> + btf = btf_vmlinux;
>>> + btf_get(btf);
>>> + }
>>> +
>>> + st_ops_desc = bpf_struct_ops_find_value(btf,
>>> attr->btf_vmlinux_value_type_id);
>>> + if (!st_ops_desc) {
>>> + ret = -ENOTSUPP;
>>> + goto errout;
>>> + }
>>> vt = st_ops_desc->value_type;
>>> - if (attr->value_size != vt->size)
>>> - return ERR_PTR(-EINVAL);
>>> + if (attr->value_size != vt->size) {
>>> + ret = -EINVAL;
>>> + goto errout;
>>> + }
>>> t = st_ops_desc->type;
>>> @@ -694,17 +710,18 @@ static struct bpf_map *bpf_struct_ops_map_alloc(union
>>> bpf_attr *attr)
>>> (vt->size - sizeof(struct bpf_struct_ops_value));
>>> st_map = bpf_map_area_alloc(st_map_size, NUMA_NO_NODE);
>>> - if (!st_map)
>>> - return ERR_PTR(-ENOMEM);
>>> + if (!st_map) {
>>> + ret = -ENOMEM;
>>> + goto errout;
>>> + }
>>> + st_map->btf = btf;
>>
>> How about do the "st_map->btf = btf;" assignment the same as where the current
>> code is doing (a few lines below). Would it avoid the new "btf = NULL;" dance
>> during the error case?
>>
>> nit, if moving a line, I would move the following "st_map->st_ops_desc =
>> st_ops_desc;" to the later and close to where "st_map->btf = btf;" is.
>
> It would work. But, I also need to init st_map->btf as NULL. Or, it may
> fail at errout_free to free an invalid pointer if I read it correctly.
st_map->btf should have been initialized to NULL. Please check bpf_map_area_alloc().
next prev parent reply other threads:[~2023-11-27 22:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 20:12 [PATCH bpf-next v11 00/13] Registrating struct_ops types from modules thinker.li
2023-11-06 20:12 ` [PATCH bpf-next v11 01/13] bpf: refactory struct_ops type initialization to a function thinker.li
2023-11-10 1:11 ` Martin KaFai Lau
2023-11-21 23:53 ` Kui-Feng Lee
2023-11-06 20:12 ` [PATCH bpf-next v11 02/13] bpf: get type information with BPF_ID_LIST thinker.li
2023-11-06 20:12 ` [PATCH bpf-next v11 03/13] bpf, net: introduce bpf_struct_ops_desc thinker.li
2023-11-06 20:12 ` [PATCH bpf-next v11 04/13] bpf: add struct_ops_tab to btf thinker.li
2023-11-10 1:35 ` Martin KaFai Lau
2023-11-22 2:27 ` Kui-Feng Lee
2023-11-06 20:12 ` [PATCH bpf-next v11 05/13] bpf: make struct_ops_map support btfs other than btf_vmlinux thinker.li
2023-11-10 1:40 ` Martin KaFai Lau
2023-11-22 2:28 ` Kui-Feng Lee
2023-11-06 20:12 ` [PATCH bpf-next v11 06/13] bpf: lookup struct_ops types from a given module BTF thinker.li
2023-11-06 20:12 ` [PATCH bpf-next v11 07/13] bpf: pass attached BTF to the bpf_struct_ops subsystem thinker.li
2023-11-10 2:04 ` Martin KaFai Lau
2023-11-22 22:33 ` Kui-Feng Lee
2023-11-27 22:08 ` Martin KaFai Lau [this message]
2023-11-06 20:12 ` [PATCH bpf-next v11 08/13] bpf: hold module for bpf_struct_ops_map thinker.li
2023-11-06 20:12 ` [PATCH bpf-next v11 09/13] bpf: validate value_type thinker.li
2023-11-10 2:11 ` Martin KaFai Lau
2023-11-22 23:47 ` Kui-Feng Lee
2023-11-06 20:12 ` [PATCH bpf-next v11 10/13] bpf, net: switch to dynamic registration thinker.li
2023-11-10 2:19 ` Martin KaFai Lau
2023-11-22 23:53 ` Kui-Feng Lee
2023-11-06 20:12 ` [PATCH bpf-next v11 11/13] libbpf: Find correct module BTFs for struct_ops maps and progs thinker.li
2023-11-06 20:12 ` [PATCH bpf-next v11 12/13] bpf: export btf_ctx_access to modules thinker.li
2023-11-06 20:12 ` [PATCH bpf-next v11 13/13] selftests/bpf: test case for register_bpf_struct_ops() thinker.li
2023-11-10 2:23 ` Martin KaFai Lau
2023-11-22 23:59 ` Kui-Feng Lee
2023-11-17 10:45 ` Hou Tao
2023-11-23 0:00 ` Kui-Feng Lee
2023-11-10 6:56 ` [PATCH bpf-next v11 00/13] Registrating struct_ops types from modules Martin KaFai Lau
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=4880ee9f-780c-4b7c-a292-578212da8273@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=drosen@google.com \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=sinquersw@gmail.com \
--cc=song@kernel.org \
--cc=thinker.li@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.