From: Anton Protopopov <aspsk@isovalent.com>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 3/5] bpf: add fd_array_cnt attribute for prog_load
Date: Sun, 17 Nov 2024 21:24:30 +0000 [thread overview]
Message-ID: <ZzpfDvL8CeiZCztK@eis> (raw)
In-Reply-To: <a21258aa3de7f478ff7144d0d453adc610f3797b.camel@gmail.com>
On 24/11/15 07:06PM, Eduard Zingerman wrote:
> On Fri, 2024-11-15 at 00:46 +0000, Anton Protopopov wrote:
>
> [...]
>
> > @@ -22537,6 +22543,76 @@ struct btf *bpf_get_btf_vmlinux(void)
> > return btf_vmlinux;
> > }
> >
> > +/*
> > + * The add_fd_from_fd_array() is executed only if fd_array_cnt is given. In
> > + * this case expect that every file descriptor in the array is either a map or
> > + * a BTF, or a hole (0). Everything else is considered to be trash.
> > + */
> > +static int add_fd_from_fd_array(struct bpf_verifier_env *env, int fd)
> > +{
> > + struct bpf_map *map;
> > + CLASS(fd, f)(fd);
> > + int ret;
> > +
> > + map = __bpf_map_get(f);
> > + if (IS_ERR(map)) {
> > + if (!IS_ERR(__btf_get_by_fd(f)))
> > + return 0;
> > +
> > + /* allow holes */
> > + if (!fd)
> > + return 0;
> > +
> > + verbose(env, "fd %d is not pointing to valid bpf_map or btf\n", fd);
> > + return PTR_ERR(map);
> > + }
> > +
> > + ret = add_used_map(env, map);
> > + if (ret < 0)
> > + return ret;
> > + return 0;
> > +}
>
> Nit: keeping this function "flat" would allow easier extension, if necessary.
> E.g.:
>
> static int add_fd_from_fd_array(struct bpf_verifier_env *env, int fd)
> {
> struct bpf_map *map;
> CLASS(fd, f)(fd);
> int ret;
>
> /* allow holes */
> if (!fd) {
> return 0;
> }
> map = __bpf_map_get(f);
> if (!IS_ERR(map)) {
> ret = add_used_map(env, map);
> return ret < 0 ? ret : 0;
> }
> if (!IS_ERR(__btf_get_by_fd(f))) {
> return 0;
> }
> verbose(env, "fd %d is not pointing to valid bpf_map or btf\n", fd);
> return -EINVAL;
> }
Thanks, this makes sense, I will change it to a flat version in v2.
> [...]
next prev parent reply other threads:[~2024-11-17 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 0:46 [PATCH bpf-next 0/5] Add fd_array_cnt attribute for BPF_PROG_LOAD Anton Protopopov
2024-11-15 0:46 ` [PATCH bpf-next 1/5] bpf: add a __btf_get_by_fd helper Anton Protopopov
2024-11-15 0:46 ` [PATCH bpf-next 2/5] bpf: move map/prog compatibility checks Anton Protopopov
2024-11-15 0:46 ` [PATCH bpf-next 3/5] bpf: add fd_array_cnt attribute for prog_load Anton Protopopov
2024-11-16 3:06 ` Eduard Zingerman
2024-11-17 21:24 ` Anton Protopopov [this message]
2024-11-15 0:46 ` [PATCH bpf-next 4/5] selftests/bpf: Add tests for fd_array_cnt Anton Protopopov
2024-11-16 3:06 ` Eduard Zingerman
2024-11-17 21:30 ` Anton Protopopov
2024-11-15 0:46 ` [PATCH bpf-next 5/5] bpf: fix potential error return Anton Protopopov
2024-11-16 3:06 ` [PATCH bpf-next 0/5] Add fd_array_cnt attribute for BPF_PROG_LOAD Eduard Zingerman
2024-11-17 21:22 ` Anton Protopopov
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=ZzpfDvL8CeiZCztK@eis \
--to=aspsk@isovalent.com \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@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