From: sashiko-bot@kernel.org
To: "Abhinav Madake" <abhinavmadake@gmail.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] libbpf: Return -EINVAL from btf__align_of() for unknown type ID
Date: Sat, 19 Sep 2026 16:57:18 +0000 [thread overview]
Message-ID: <20260919165718.9C3B51F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260919164229.95154-1-abhinavmadake@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] bpf: btf__align_of() negative error breaks btf_dump.c
--
commit d6024f50b48c7fc7873ce247e9f420706729d50a
Author: Abhinav Madake <abhinavmadake@gmail.com>
libbpf: Return -EINVAL from btf__align_of() for unknown type ID
btf__align_of() passes the result of btf__type_by_id() straight to
btf_kind() without checking for NULL, so an unknown type ID
dereferences a NULL pointer instead of returning an error like the
other btf__*() lookups do.
BTF parsed from raw data cannot trigger this, since btf_sanity_check()
rejects dangling references. BTF built with the btf__add_*() API can:
those only check the ID range, so a forward reference to a type that
was never added, followed by btf__align_of() on it (directly, or
through the recursive struct/array/typedef cases), crashes.
Check for NULL and return -EINVAL, matching btf__type_by_id().
Link: https://github.com/libbpf/libbpf/issues/983
> diff --git a/tools/lib/bpf/btf.c b/tools/lib/bpf/btf.c
> index 908bd344229d5..d15bc09ac53de 100644
> --- a/tools/lib/bpf/btf.c
> +++ b/tools/lib/bpf/btf.c
> @@ -986,8 +986,12 @@ __s64 btf__resolve_size(const struct btf *btf, __u32 type_id)
> int btf__align_of(const struct btf *btf, __u32 id)
> {
> const struct btf_type *t = btf__type_by_id(btf, id);
> - __u16 kind = btf_kind(t);
> + __u16 kind;
>
> + if (!t)
> + return libbpf_err(-EINVAL);
[Severity: Medium]
Will this negative return value break callers in tools/lib/bpf/btf_dump.c
that expect 0 on error?
When btf_dump.c processes invalid BTF types, this -EINVAL return bypasses
checks for 0, leading to modulo operations with a negative number promoted
to a large unsigned integer.
In ptr_is_aligned(), the negative alignment bypasses the check for 0:
tools/lib/bpf/btf_dump.c:ptr_is_aligned() {
int alignment = btf__align_of(btf, type_id);
if (alignment == 0)
return false;
return ((uintptr_t)data) % alignment == 0;
}
In btf_is_struct_packed(), the error bypasses the false-check (which
expects 0), causing an invalid modulo operation with 8 * -22 promoted
to unsigned:
tools/lib/bpf/btf_dump.c:btf_is_struct_packed() {
...
align = btf__align_of(btf, m->type);
bit_sz = btf_member_bitfield_size(t, i);
if (align && bit_sz == 0 && m->offset % (8 * align) != 0)
return true;
...
}
Should the callers in btf_dump.c be updated to handle negative return
values?
> +
> + kind = btf_kind(t);
> switch (kind) {
> case BTF_KIND_INT:
> case BTF_KIND_ENUM:
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260919164229.95154-1-abhinavmadake@gmail.com?part=1
next prev parent reply other threads:[~2026-09-19 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 16:42 [PATCH bpf-next] libbpf: Return -EINVAL from btf__align_of() for unknown type ID Abhinav Madake
2026-09-19 16:57 ` sashiko-bot [this message]
2026-09-19 17:45 ` [PATCH bpf-next v2] libbpf: Check for unknown type ID in btf__align_of() Abhinav Madake
2026-09-19 18:44 ` Alexei Starovoitov
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=20260919165718.9C3B51F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=abhinavmadake@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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