From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bot+bpf-ci@kernel.org, alan.maguire@oracle.com, ast@kernel.org,
arighi@nvidia.com, akpm@linux-foundation.org, andrii@kernel.org,
morbo@google.com, changwoo@igalia.com, daniel@iogearbox.net,
void@manifault.com, dolinux.peng@gmail.com, eddyz87@gmail.com,
haoluo@google.com, jolsa@kernel.org, john.fastabend@gmail.com,
corbet@lwn.net, justinstitt@google.com, kpsingh@kernel.org,
martin.lau@linux.dev, nathan@kernel.org,
nick.desaulniers+lkml@gmail.com, nsc@kernel.org,
shuah@kernel.org, song@kernel.org, sdf@fomichev.me,
tj@kernel.org, yonghong.song@linux.dev, bpf@vger.kernel.org,
dwarves@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, sched-ext@lists.linux.dev,
martin.lau@kernel.org, clm@meta.com
Subject: Re: [PATCH bpf-next v4 3/8] resolve_btfids: Introduce enum btf_id_kind
Date: Thu, 18 Dec 2025 12:03:19 -0800 [thread overview]
Message-ID: <113fe7cd-210c-4c4f-8703-f289010fd049@linux.dev> (raw)
In-Reply-To: <CAEf4BzZXzQ6fZetTA8Trwa_pu7o1AJuMyUuHbW9YXHYGQL-_HA@mail.gmail.com>
On 12/18/25 11:58 AM, Andrii Nakryiko wrote:
> On Thu, Dec 18, 2025 at 9:47 AM Ihor Solodrai <ihor.solodrai@linux.dev> wrote:
>>
>> On 12/17/25 4:47 PM, bot+bpf-ci@kernel.org wrote:
>>>> diff --git a/tools/bpf/resolve_btfids/main.c b/tools/bpf/resolve_btfids/main.c
>>>> index b4caae1170dd..da8c7d127632 100644
>>>> --- a/tools/bpf/resolve_btfids/main.c
>>>> +++ b/tools/bpf/resolve_btfids/main.c
>>>
>>> [ ... ]
>>>
>>>> @@ -260,22 +279,36 @@ static char *get_id(const char *prefix_end)
>>>> return id;
>>>> }
>>>>
>>>> -static struct btf_id *add_set(struct object *obj, char *name, bool is_set8)
>>>> +static struct btf_id *add_set(struct object *obj, char *name, enum btf_id_kind kind)
>>>> {
>>>> + int len = strlen(name);
>>>> + int prefixlen;
>>>> + char *id;
>>>> +
>>>> /*
>>>> * __BTF_ID__set__name
>>>> * name = ^
>>>> * id = ^
>>>> */
>>>> - char *id = name + (is_set8 ? sizeof(BTF_SET8 "__") : sizeof(BTF_SET "__")) - 1;
>>>> - int len = strlen(name);
>>>> + switch (kind) {
>>>> + case BTF_ID_KIND_SET:
>>>> + prefixlen = sizeof(BTF_SET "__") - 1;
>>>> + break;
>>>> + case BTF_ID_KIND_SET8:
>>>> + prefixlen = sizeof(BTF_SET8 "__") - 1;
>>>> + break;
>>>> + default:
>>>> + pr_err("Unexpected kind %d passed to %s() for symbol %s\n", kind, __func__, name);
>>>> + return NULL;
>>>> + }
>>>> +
>>>> + id = name + prefixlen - 1;
>>>
>>> Is this off by one? The original code computed:
>>>
>>> id = name + sizeof(BTF_SET "__") - 1
>>>
>>> For BTF_SET ("set"), this gives: name + sizeof("set__") - 1 = name + 6 - 1 = name + 5
>>>
>>> The new code computes:
>>>
>>> prefixlen = sizeof(BTF_SET "__") - 1 = 6 - 1 = 5
>>> id = name + prefixlen - 1 = name + 5 - 1 = name + 4
>>>
>>> The -1 appears to be applied twice now, once in the prefixlen assignment and
>>> again when computing id. Should this line be:
>>>
>>> id = name + prefixlen;
>>
>> Yes, this is an off-by-one bug.
>>
>> Good catch, Opus 4.5. Sonnet 4.5 missed this in v3.
>>
>> This was "harmless", since the names stored in the trees don't affect
>> the output. The comparison between the names still works, as they all
>> simply got a "_" prefix. But this only makes the bug sneaky, which is
>> very bad.
>>
>> The suggested fix is meh though, IMO a better one is:
>
> the bug is not in determining prefix length, but in using it to find
> where id starts in the string, so the fix should be
>
> id = name + prefixlen;
>
> prefixlen is calculated correctly, IMO
Aaahh, because the null byte is counted by sizeof, right... I missed that.
>
>>
>> [...]
>>
next prev parent reply other threads:[~2025-12-18 20:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 0:33 [PATCH bpf-next v4 0/8] resolve_btfids: Support for BTF modifications Ihor Solodrai
2025-12-18 0:33 ` [PATCH bpf-next v4 1/8] resolve_btfids: Rename object btf field to btf_path Ihor Solodrai
2025-12-18 0:33 ` [PATCH bpf-next v4 2/8] resolve_btfids: Factor out load_btf() Ihor Solodrai
2025-12-18 0:33 ` [PATCH bpf-next v4 3/8] resolve_btfids: Introduce enum btf_id_kind Ihor Solodrai
2025-12-18 0:47 ` bot+bpf-ci
2025-12-18 17:46 ` Ihor Solodrai
2025-12-18 19:58 ` Andrii Nakryiko
2025-12-18 20:03 ` Ihor Solodrai [this message]
2025-12-18 0:33 ` [PATCH bpf-next v4 4/8] resolve_btfids: Always build with -Wall -Werror Ihor Solodrai
2025-12-18 0:33 ` [PATCH bpf-next v4 5/8] kbuild: Sync kconfig when PAHOLE_VERSION changes Ihor Solodrai
2025-12-18 19:21 ` Eduard Zingerman
2025-12-18 21:33 ` Ihor Solodrai
2025-12-18 22:36 ` Eduard Zingerman
2025-12-18 21:01 ` Andrii Nakryiko
2025-12-18 0:33 ` [PATCH bpf-next v4 6/8] lib/Kconfig.debug: Set the minimum required pahole version to v1.22 Ihor Solodrai
2025-12-18 0:33 ` [PATCH bpf-next v4 7/8] selftests/bpf: Run resolve_btfids only for relevant .test.o objects Ihor Solodrai
2025-12-18 19:22 ` Eduard Zingerman
2025-12-18 0:33 ` [PATCH bpf-next v4 8/8] resolve_btfids: Change in-place update with raw binary output Ihor Solodrai
2025-12-18 17:54 ` Ihor Solodrai
2025-12-18 21:15 ` Andrii Nakryiko
2025-12-18 22:39 ` Eduard Zingerman
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=113fe7cd-210c-4c4f-8703-f289010fd049@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=alan.maguire@oracle.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=arighi@nvidia.com \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=changwoo@igalia.com \
--cc=clm@meta.com \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=dolinux.peng@gmail.com \
--cc=dwarves@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=kpsingh@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nsc@kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.com \
--cc=yonghong.song@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 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.