From: Martin KaFai Lau <martin.lau@linux.dev>
To: Kui-Feng Lee <thinker.li@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, song@kernel.org,
kernel-team@meta.com, andrii@kernel.org, sinquersw@gmail.com,
kuifeng@meta.com
Subject: Re: [PATCH bpf-next v4 2/7] bpf: enable detaching links of struct_ops objects.
Date: Thu, 23 May 2024 11:09:44 -0700 [thread overview]
Message-ID: <025ebd13-fcd1-4abe-b5c1-d845c057200d@linux.dev> (raw)
In-Reply-To: <20240521225121.770930-3-thinker.li@gmail.com>
On 5/21/24 3:51 PM, Kui-Feng Lee wrote:
> Implement the detach callback in bpf_link_ops for struct_ops so that user
> programs can detach a struct_ops link. The subsystems that struct_ops
> objects are registered to can also use this callback to detach the links
> being passed to them.
>
> Signed-off-by: Kui-Feng Lee <thinker.li@gmail.com>
> ---
> kernel/bpf/bpf_struct_ops.c | 63 +++++++++++++++++++++++++++++++++----
> 1 file changed, 57 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/bpf/bpf_struct_ops.c b/kernel/bpf/bpf_struct_ops.c
> index 1542dded7489..fb6e8a3190ef 100644
> --- a/kernel/bpf/bpf_struct_ops.c
> +++ b/kernel/bpf/bpf_struct_ops.c
> @@ -1057,9 +1057,6 @@ static void bpf_struct_ops_map_link_dealloc(struct bpf_link *link)
> st_map = (struct bpf_struct_ops_map *)
> rcu_dereference_protected(st_link->map, true);
> if (st_map) {
> - /* st_link->map can be NULL if
> - * bpf_struct_ops_link_create() fails to register.
> - */
> st_map->st_ops_desc->st_ops->unreg(&st_map->kvalue.data, link);
> bpf_map_put(&st_map->map);
> }
> @@ -1075,7 +1072,8 @@ static void bpf_struct_ops_map_link_show_fdinfo(const struct bpf_link *link,
> st_link = container_of(link, struct bpf_struct_ops_link, link);
> rcu_read_lock();
> map = rcu_dereference(st_link->map);
> - seq_printf(seq, "map_id:\t%d\n", map->id);
> + if (map)
> + seq_printf(seq, "map_id:\t%d\n", map->id);
> rcu_read_unlock();
> }
>
> @@ -1088,7 +1086,8 @@ static int bpf_struct_ops_map_link_fill_link_info(const struct bpf_link *link,
> st_link = container_of(link, struct bpf_struct_ops_link, link);
> rcu_read_lock();
> map = rcu_dereference(st_link->map);
> - info->struct_ops.map_id = map->id;
> + if (map)
> + info->struct_ops.map_id = map->id;
> rcu_read_unlock();
> return 0;
> }
> @@ -1113,6 +1112,10 @@ static int bpf_struct_ops_map_link_update(struct bpf_link *link, struct bpf_map
> mutex_lock(&update_mutex);
>
> old_map = rcu_dereference_protected(st_link->map, lockdep_is_held(&update_mutex));
> + if (!old_map) {
> + err = -EINVAL;
Just noticed this while checking the return value in patch 3.
This should be -ENOLINK such that it is consistent to the other links'
.update_prog (e.g. cgroup, tcx, net_namespace...).
> + goto err_out;
> + }
> if (expected_old_map && old_map != expected_old_map) {
> err = -EPERM;
> goto err_out;
> @@ -1139,8 +1142,37 @@ static int bpf_struct_ops_map_link_update(struct bpf_link *link, struct bpf_map
> return err;
> }
>
> +static int bpf_struct_ops_map_link_detach(struct bpf_link *link)
> +{
> + struct bpf_struct_ops_link *st_link = container_of(link, struct bpf_struct_ops_link, link);
> + struct bpf_struct_ops_map *st_map;
> + struct bpf_map *map;
> +
> + mutex_lock(&update_mutex);
> +
> + map = rcu_dereference_protected(st_link->map, lockdep_is_held(&update_mutex));
> + if (!map) {
> + mutex_unlock(&update_mutex);
> + return -EINVAL;
Same here but should be always 0 (detach always succeeds).
> + }
> + st_map = container_of(map, struct bpf_struct_ops_map, map);
> +
> + st_map->st_ops_desc->st_ops->unreg(&st_map->kvalue.data, link);
> +
> + rcu_assign_pointer(st_link->map, NULL);
> + /* Pair with bpf_map_get() in bpf_struct_ops_link_create() or
> + * bpf_map_inc() in bpf_struct_ops_map_link_update().
> + */
> + bpf_map_put(&st_map->map);
> +
> + mutex_unlock(&update_mutex);
> +
> + return 0;
> +}
> +
> static const struct bpf_link_ops bpf_struct_ops_map_lops = {
> .dealloc = bpf_struct_ops_map_link_dealloc,
> + .detach = bpf_struct_ops_map_link_detach,
> .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,
> @@ -1176,13 +1208,32 @@ int bpf_struct_ops_link_create(union bpf_attr *attr)
> if (err)
> goto err_out;
>
> + /* Init link->map before calling reg() in case being detached
> + * immediately.
> + */
> + RCU_INIT_POINTER(link->map, map);
> +
> + /* Once reg() is called, the object and link is already available
> + * to the subsystem, and it can call
> + * bpf_struct_ops_map_link_detach() to unreg() it. However, it is
> + * sfae not holding update_mutex here.
> + *
> + * In the case of failure in reg(), the subsystem has no reason to
> + * call bpf_struct_ops_map_link_detach() since the object is not
> + * accepted by it. In the case of success, the subsystem may call
> + * bpf_struct_ops_map_link_detach() to unreg() it, but we don't
> + * change the content of the link anymore except changing link->id
> + * in bpf_link_settle(). So, it is safe to not hold update_mutex
> + * here.
After sleeping on the RCU_INIT_POINTER dance and re-reading this comment, I need
to walk back my early reply.
Instead of having comment to explain the RCU_INIT_POINTER dance (resetting it to
NULL on reg() err because bpf_struct_ops_map_link_dealloc is not supposed to
unreg when the reg did fail), how about simplifying it and just take the
update_mutex here such that the subsystem cannot detach until the
RCU_INIT_POINTER(link->map, map) is done. Performance is not a concern here, so
I would prefer simplicity.
> + */
> err = st_map->st_ops_desc->st_ops->reg(st_map->kvalue.data, &link->link);
> if (err) {
> + RCU_INIT_POINTER(link->map, NULL);
> bpf_link_cleanup(&link_primer);
> + /* The link has been free by bpf_link_cleanup() */
> link = NULL;
> goto err_out;
> }
> - RCU_INIT_POINTER(link->map, map);
>
> return bpf_link_settle(&link_primer);
>
next prev parent reply other threads:[~2024-05-23 18:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 22:51 [PATCH bpf-next v4 0/7] Notify user space when a struct_ops object is detached/unregistered Kui-Feng Lee
2024-05-21 22:51 ` [PATCH bpf-next v4 1/7] bpf: pass bpf_struct_ops_link to callbacks in bpf_struct_ops Kui-Feng Lee
2024-05-21 22:51 ` [PATCH bpf-next v4 2/7] bpf: enable detaching links of struct_ops objects Kui-Feng Lee
2024-05-23 18:09 ` Martin KaFai Lau [this message]
2024-05-23 18:28 ` Kui-Feng Lee
2024-05-21 22:51 ` [PATCH bpf-next v4 3/7] bpf: support epoll from bpf struct_ops links Kui-Feng Lee
2024-05-23 17:23 ` Martin KaFai Lau
2024-05-23 18:24 ` Kui-Feng Lee
2024-05-23 18:34 ` Martin KaFai Lau
2024-05-23 19:03 ` Kui-Feng Lee
2024-05-23 19:10 ` Martin KaFai Lau
2024-05-23 19:28 ` Kui-Feng Lee
2024-05-21 22:51 ` [PATCH bpf-next v4 4/7] bpf: export bpf_link_inc_not_zero Kui-Feng Lee
2024-05-21 22:51 ` [PATCH bpf-next v4 5/7] selftests/bpf: test struct_ops with epoll Kui-Feng Lee
2024-05-21 22:51 ` [PATCH bpf-next v4 6/7] selftests/bpf: detach a struct_ops link from the subsystem managing it Kui-Feng Lee
2024-05-21 22:51 ` [PATCH bpf-next v4 7/7] selftests/bpf: make sure bpf_testmod handling racing link destroying well 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=025ebd13-fcd1-4abe-b5c1-d845c057200d@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox