From: Jiri Olsa <olsajiri@gmail.com>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, alan.maguire@oracle.com,
eddyz87@gmail.com
Subject: Re: [PATCH bpf-next 2/5] libbpf: make use of BTF field iterator in BPF linker code
Date: Tue, 4 Jun 2024 13:02:51 +0200 [thread overview]
Message-ID: <Zl70W3wstHhF-6zo@krava> (raw)
In-Reply-To: <20240603231720.1893487-3-andrii@kernel.org>
On Mon, Jun 03, 2024 at 04:17:16PM -0700, Andrii Nakryiko wrote:
> Switch all BPF linker code dealing with iterating BTF type ID and string
> offset fields to new btf_field_iter facilities.
>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
> ---
> tools/lib/bpf/linker.c | 60 ++++++++++++++++++++++++++----------------
> 1 file changed, 38 insertions(+), 22 deletions(-)
>
> diff --git a/tools/lib/bpf/linker.c b/tools/lib/bpf/linker.c
> index 0d4be829551b..be6539e59cf6 100644
> --- a/tools/lib/bpf/linker.c
> +++ b/tools/lib/bpf/linker.c
> @@ -957,19 +957,35 @@ static int check_btf_str_off(__u32 *str_off, void *ctx)
> static int linker_sanity_check_btf(struct src_obj *obj)
> {
> struct btf_type *t;
> - int i, n, err = 0;
> + int i, n, err;
>
> if (!obj->btf)
> return 0;
>
> n = btf__type_cnt(obj->btf);
> for (i = 1; i < n; i++) {
> + struct btf_field_iter it;
> + __u32 *type_id, *str_off;
> + const char *s;
> +
> t = btf_type_by_id(obj->btf, i);
>
> - err = err ?: btf_type_visit_type_ids(t, check_btf_type_id, obj->btf);
> - err = err ?: btf_type_visit_str_offs(t, check_btf_str_off, obj->btf);
> + err = btf_field_iter_init(&it, t, BTF_FIELD_ITER_IDS);
> if (err)
> return err;
> + while ((type_id = btf_field_iter_next(&it))) {
> + if (*type_id >= n)
> + return -EINVAL;
> + }
> +
> + err = btf_field_iter_init(&it, t, BTF_FIELD_ITER_STRS);
> + if (err)
> + return err;
> + while ((str_off = btf_field_iter_next(&it))) {
> + s = btf__str_by_offset(obj->btf, *str_off);
> + if (!s)
> + return -EINVAL;
nit, we could drop 's' and just do (!btf__str_by_offset(obj->btf, *str_off))
otherwise the patchset lgtm
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
> + }
> }
>
> return 0;
> @@ -2234,26 +2250,10 @@ static int linker_fixup_btf(struct src_obj *obj)
> return 0;
> }
SNIP
next prev parent reply other threads:[~2024-06-04 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 23:17 [PATCH bpf-next 0/5] libbpf: BTF field iterator Andrii Nakryiko
2024-06-03 23:17 ` [PATCH bpf-next 1/5] libbpf: add " Andrii Nakryiko
2024-06-04 20:37 ` Eduard Zingerman
2024-06-04 21:40 ` Andrii Nakryiko
2024-06-04 22:08 ` Eduard Zingerman
2024-06-03 23:17 ` [PATCH bpf-next 2/5] libbpf: make use of BTF field iterator in BPF linker code Andrii Nakryiko
2024-06-04 11:02 ` Jiri Olsa [this message]
2024-06-04 18:29 ` Andrii Nakryiko
2024-06-03 23:17 ` [PATCH bpf-next 3/5] libbpf: make use of BTF field iterator in BTF handling code Andrii Nakryiko
2024-06-03 23:17 ` [PATCH bpf-next 4/5] bpftool: use BTF field iterator in btfgen Andrii Nakryiko
2024-06-04 0:32 ` Quentin Monnet
2024-06-03 23:17 ` [PATCH bpf-next 5/5] libbpf: remove callback-based type/string BTF field visitor helpers Andrii Nakryiko
2024-06-04 20:56 ` [PATCH bpf-next 0/5] libbpf: BTF field iterator Eduard Zingerman
2024-06-05 10:11 ` Alan Maguire
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=Zl70W3wstHhF-6zo@krava \
--to=olsajiri@gmail.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=martin.lau@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