From: Yonghong Song <yonghong.song@linux.dev>
To: David Vernet <void@manifault.com>, bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
tj@kernel.org, clm@meta.com, thinker.li@gmail.com
Subject: Re: [PATCH bpf-next] bpf: Support default .validate() and .update() behavior for struct_ops links
Date: Thu, 10 Aug 2023 23:43:26 -0700 [thread overview]
Message-ID: <371c72e1-f2b7-8309-0329-cdffc8a3f98d@linux.dev> (raw)
In-Reply-To: <20230810220456.521517-1-void@manifault.com>
On 8/10/23 3:04 PM, David Vernet wrote:
> Currently, if a struct_ops map is loaded with BPF_F_LINK, it must also
> define the .validate() and .update() callbacks in its corresponding
> struct bpf_struct_ops in the kernel. Enabling struct_ops link is useful
> in its own right to ensure that the map is unloaded if an application
> crashes. For example, with sched_ext, we want to automatically unload
> the host-wide scheduler if the application crashes. We would likely
> never support updating elements of a sched_ext struct_ops map, so we'd
> have to implement these callbacks showing that they _can't_ support
> element updates just to benefit from the basic lifetime management of
> struct_ops links.
>
> Let's enable struct_ops maps to work with BPF_F_LINK even if they
> haven't defined these callbacks, by assuming that a struct_ops map
> element cannot be updated by default.
Maybe you want to add one map_flag to indicate validate/update callbacks
are optional for a struct_ops link? In this case, some struct_ops maps
can still require validate() and update(), but others can skip them?
>
> Signed-off-by: David Vernet <void@manifault.com>
> ---
> kernel/bpf/bpf_struct_ops.c | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/bpf/bpf_struct_ops.c b/kernel/bpf/bpf_struct_ops.c
> index eaff04eefb31..3d2fb85186a9 100644
> --- a/kernel/bpf/bpf_struct_ops.c
> +++ b/kernel/bpf/bpf_struct_ops.c
> @@ -509,9 +509,12 @@ static long bpf_struct_ops_map_update_elem(struct bpf_map *map, void *key,
> }
>
> if (st_map->map.map_flags & BPF_F_LINK) {
> - err = st_ops->validate(kdata);
> - if (err)
> - goto reset_unlock;
> + err = 0;
> + if (st_ops->validate) {
> + err = st_ops->validate(kdata);
> + if (err)
> + goto reset_unlock;
> + }
> set_memory_rox((long)st_map->image, 1);
> /* Let bpf_link handle registration & unregistration.
> *
> @@ -663,9 +666,6 @@ static struct bpf_map *bpf_struct_ops_map_alloc(union bpf_attr *attr)
> if (attr->value_size != vt->size)
> return ERR_PTR(-EINVAL);
>
> - if (attr->map_flags & BPF_F_LINK && (!st_ops->validate || !st_ops->update))
> - return ERR_PTR(-EOPNOTSUPP);
> -
> t = st_ops->type;
>
> st_map_size = sizeof(*st_map) +
> @@ -838,6 +838,11 @@ static int bpf_struct_ops_map_link_update(struct bpf_link *link, struct bpf_map
> goto err_out;
> }
>
> + if (!st_map->st_ops->update) {
> + err = -EOPNOTSUPP;
> + goto err_out;
> + }
> +
> err = st_map->st_ops->update(st_map->kvalue.data, old_st_map->kvalue.data);
> if (err)
> goto err_out;
next prev parent reply other threads:[~2023-08-11 6:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 22:04 [PATCH bpf-next] bpf: Support default .validate() and .update() behavior for struct_ops links David Vernet
2023-08-10 22:46 ` Stanislav Fomichev
2023-08-10 23:01 ` David Vernet
2023-08-10 23:15 ` Stanislav Fomichev
2023-08-11 17:35 ` Martin KaFai Lau
2023-08-11 18:17 ` Kui-Feng Lee
2023-08-11 20:19 ` David Vernet
2023-08-11 21:25 ` Kui-Feng Lee
2023-08-11 22:49 ` Martin KaFai Lau
2023-08-11 23:12 ` Kui-Feng Lee
2023-08-11 23:34 ` Martin KaFai Lau
2023-08-11 23:36 ` David Vernet
2023-08-14 16:55 ` Martin KaFai Lau
2023-08-14 17:45 ` David Vernet
2023-08-11 6:22 ` Kui-Feng Lee
2023-08-11 15:10 ` David Vernet
2023-08-11 6:43 ` Yonghong Song [this message]
2023-08-11 15:09 ` David Vernet
2023-08-11 15:43 ` Yonghong Song
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=371c72e1-f2b7-8309-0329-cdffc8a3f98d@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=thinker.li@gmail.com \
--cc=tj@kernel.org \
--cc=void@manifault.com \
--cc=yhs@fb.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.