From: Kui-Feng Lee <sinquersw@gmail.com>
To: Martin KaFai Lau <martin.lau@linux.dev>, Kui-Feng Lee <kuifeng@meta.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, song@kernel.org,
kernel-team@meta.com, andrii@kernel.org, sdf@google.com
Subject: Re: [PATCH bpf-next v7 5/8] bpf: Update the struct_ops of a bpf_link.
Date: Fri, 17 Mar 2023 18:11:57 -0700 [thread overview]
Message-ID: <6fed9361-ba07-c387-14d4-2fee2d161b5f@gmail.com> (raw)
In-Reply-To: <690c5fff-4828-c849-c946-1f1a29e168c8@linux.dev>
On 3/17/23 12:23, Martin KaFai Lau wrote:
> On 3/15/23 7:36 PM, Kui-Feng Lee wrote:
>> +static int bpf_struct_ops_map_link_update(struct bpf_link *link,
>> struct bpf_map *new_map)
>> +{
>> + struct bpf_struct_ops_map *st_map, *old_st_map;
>> + struct bpf_struct_ops_link *st_link;
>> + struct bpf_map *old_map;
>> + int err = 0;
>> +
>> + st_link = container_of(link, struct bpf_struct_ops_link, link);
>> + st_map = container_of(new_map, struct bpf_struct_ops_map, map);
>> +
>> + if (!bpf_struct_ops_valid_to_reg(new_map))
>> + return -EINVAL;
>> +
>> + mutex_lock(&update_mutex);
>> +
>> + old_map = rcu_dereference_protected(st_link->map,
>> lockdep_is_held(&update_mutex));
>> + old_st_map = container_of(old_map, struct bpf_struct_ops_map, map);
>> + /* The new and old struct_ops must be the same type. */
>> + if (st_map->st_ops != old_st_map->st_ops) {
>> + err = -EINVAL;
>> + goto err_out;
>> + }
>> +
>> + err = st_map->st_ops->update(st_map->kvalue.data,
>> old_st_map->kvalue.data);
>
> I don't think it has completely addressed Andrii's comment in v4
> regarding BPF_F_REPLACE:
> https://lore.kernel.org/bpf/CAEf4BzbK8s+VFG5HefydD7CRLzkRFKg-Er0PKV_-C2-yttfXzA@mail.gmail.com/
>
> For now, tcp_update_congestion_control() enforces the same cc-name.
> However, it is still not the same as what BPF_F_REPLACE intented to do:
> update only when it is the same old-map. Same cc-name does not
> necessarily mean the same old-map.
>
>> + if (err)
>> + goto err_out;
>> +
>> + bpf_map_inc(new_map);
>> + rcu_assign_pointer(st_link->map, new_map);
>> + bpf_map_put(old_map);
>> +
>> +err_out:
>> + mutex_unlock(&update_mutex);
>> +
>> + return err;
>> +}
>> +
>> static const struct bpf_link_ops bpf_struct_ops_map_lops = {
>> .dealloc = bpf_struct_ops_map_link_dealloc,
>> .show_fdinfo = bpf_struct_ops_map_link_show_fdinfo,
>> .fill_link_info = bpf_struct_ops_map_link_fill_link_info,
>> + .update_map = bpf_struct_ops_map_link_update,
>> };
>> int bpf_struct_ops_link_create(union bpf_attr *attr)
>> diff --git a/kernel/bpf/syscall.c b/kernel/bpf/syscall.c
>> index 5a45e3bf34e2..6fa10d108278 100644
>> --- a/kernel/bpf/syscall.c
>> +++ b/kernel/bpf/syscall.c
>> @@ -4676,6 +4676,21 @@ static int link_create(union bpf_attr *attr,
>> bpfptr_t uattr)
>> return ret;
>> }
>> +static int link_update_map(struct bpf_link *link, union bpf_attr *attr)
>> +{
>> + struct bpf_map *new_map;
>> + int ret = 0;
>
> nit. init zero is unnecessarily.
>
>> +
>> + new_map = bpf_map_get(attr->link_update.new_map_fd);
>> + if (IS_ERR(new_map))
>> + return -EINVAL;
>> +
>> + ret = link->ops->update_map(link, new_map);
>> +
>> + bpf_map_put(new_map);
>> + return ret;
>> +}
>> +
>> #define BPF_LINK_UPDATE_LAST_FIELD link_update.old_prog_fd
>> static int link_update(union bpf_attr *attr)
>> @@ -4696,6 +4711,11 @@ static int link_update(union bpf_attr *attr)
>> if (IS_ERR(link))
>> return PTR_ERR(link);
>> + if (link->ops->update_map) {
>> + ret = link_update_map(link, attr);
>> + goto out_put_link;
>> + }
>> +
>> new_prog = bpf_prog_get(attr->link_update.new_prog_fd);
>> if (IS_ERR(new_prog)) {
>> ret = PTR_ERR(new_prog);
>> diff --git a/net/bpf/bpf_dummy_struct_ops.c
>> b/net/bpf/bpf_dummy_struct_ops.c
>> index ff4f89a2b02a..158f14e240d0 100644
>> --- a/net/bpf/bpf_dummy_struct_ops.c
>> +++ b/net/bpf/bpf_dummy_struct_ops.c
>> @@ -222,12 +222,18 @@ static void bpf_dummy_unreg(void *kdata)
>> {
>> }
>> +static int bpf_dummy_update(void *kdata, void *old_kdata)
>> +{
>> + return -EOPNOTSUPP;
>> +}
>> +
>> struct bpf_struct_ops bpf_bpf_dummy_ops = {
>> .verifier_ops = &bpf_dummy_verifier_ops,
>> .init = bpf_dummy_init,
>> .check_member = bpf_dummy_ops_check_member,
>> .init_member = bpf_dummy_init_member,
>> .reg = bpf_dummy_reg,
>> + .update = bpf_dummy_update,
>
> When looking at this together in patch 5, the changes in
> bpf_dummy_struct_ops.c should not be needed.
I don't follow you.
If we don't assign a function to .update, it will fail in
bpf_struct_ops_map_link_update(). Of course, I can add a check
in bpf_struct_ops_map_link_update() to return an error if .update
is NULL.
>
>
next prev parent reply other threads:[~2023-03-18 1:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 2:36 [PATCH bpf-next v7 0/8] Transit between BPF TCP congestion controls Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 1/8] bpf: Retire the struct_ops map kvalue->refcnt Kui-Feng Lee
2023-03-17 16:47 ` Martin KaFai Lau
2023-03-17 20:41 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 2/8] net: Update an existing TCP congestion control algorithm Kui-Feng Lee
2023-03-17 15:23 ` Daniel Borkmann
2023-03-17 17:18 ` Martin KaFai Lau
2023-03-17 17:23 ` Daniel Borkmann
2023-03-17 21:46 ` Kui-Feng Lee
2023-03-17 23:07 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 3/8] bpf: Create links for BPF struct_ops maps Kui-Feng Lee
2023-03-17 18:10 ` Martin KaFai Lau
2023-03-17 20:52 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 4/8] libbpf: Create a bpf_link in bpf_map__attach_struct_ops() Kui-Feng Lee
2023-03-17 18:44 ` Martin KaFai Lau
2023-03-17 21:00 ` Kui-Feng Lee
2023-03-17 22:23 ` Andrii Nakryiko
2023-03-17 23:48 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 5/8] bpf: Update the struct_ops of a bpf_link Kui-Feng Lee
2023-03-17 19:23 ` Martin KaFai Lau
2023-03-17 21:39 ` Kui-Feng Lee
2023-03-18 1:11 ` Kui-Feng Lee [this message]
2023-03-18 5:38 ` Martin KaFai Lau
2023-03-17 22:27 ` Andrii Nakryiko
2023-03-18 0:41 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 6/8] libbpf: Update a bpf_link with another struct_ops Kui-Feng Lee
2023-03-17 19:42 ` Martin KaFai Lau
2023-03-17 21:40 ` Kui-Feng Lee
2023-03-17 22:33 ` Andrii Nakryiko
2023-03-18 1:17 ` Kui-Feng Lee
2023-03-16 2:36 ` [PATCH bpf-next v7 7/8] libbpf: Use .struct_ops.link section to indicate a struct_ops with a link Kui-Feng Lee
2023-03-17 22:35 ` Andrii Nakryiko
2023-03-16 2:36 ` [PATCH bpf-next v7 8/8] selftests/bpf: Test switching TCP Congestion Control algorithms Kui-Feng Lee
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=6fed9361-ba07-c387-14d4-2fee2d161b5f@gmail.com \
--to=sinquersw@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@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