From: Yonghong Song <yonghong.song@linux.dev>
To: Hoyeon Lee <hoyeon.lee@suse.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
"open list:BPF [LIBRARY] (libbpf)" <bpf@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:CLANG/LLVM BUILD SUPPORT:Keyword:b(?i:clang|llvm)b"
<llvm@lists.linux.dev>
Subject: Re: [RFC bpf-next 1/1] libbpf: add compile-time OOB warning to bpf_tail_call_static
Date: Thu, 4 Sep 2025 21:00:41 -0700 [thread overview]
Message-ID: <6b52caf8-51f0-45ed-8f59-11f24dd2861e@linux.dev> (raw)
In-Reply-To: <20250905025314.245650-2-hoyeon.lee@suse.com>
On 9/4/25 7:53 PM, Hoyeon Lee wrote:
> Add a compile-time check to bpf_tail_call_static() to warn when a
> constant slot(index) is >= map->max_entries. This uses a small
> BPF_MAP_ENTRIES() macro together with Clang's diagnose_if attribute.
>
> Clang front-end keeps the map type with a '(*max_entries)[N]' field,
> so the expression
>
> sizeof(*(m)->max_entries) / sizeof(**(m)->max_entries)
>
> is resolved to N entirely at compile time. This allows diagnose_if()
> to emit a warning when a constant slot index is out of range.
>
> Out-of-bounds tail call checkup is no-ops at runtime. Emitting a
> compile-time warning can help developers detect mistakes earlier. The
> check is currently limited to Clang (due to diagnose_if) and constant
> indices, but should catch common errors.
>
> Signed-off-by: Hoyeon Lee <hoyeon.lee@suse.com>
> ---
> tools/lib/bpf/bpf_helpers.h | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/tools/lib/bpf/bpf_helpers.h b/tools/lib/bpf/bpf_helpers.h
> index 80c028540656..0d9551bb90c0 100644
> --- a/tools/lib/bpf/bpf_helpers.h
> +++ b/tools/lib/bpf/bpf_helpers.h
> @@ -173,6 +173,26 @@ bpf_tail_call_static(void *ctx, const void *map, const __u32 slot)
> :: [ctx]"r"(ctx), [map]"r"(map), [slot]"i"(slot)
> : "r0", "r1", "r2", "r3", "r4", "r5");
> }
> +
> +#if __has_attribute(diagnose_if)
> +static __always_inline void __bpf_tail_call_warn(int oob)
> + __attribute__((diagnose_if(oob, "bpf_tail_call: slot >= max_entries", "warning")));
> +
> +#define BPF_MAP_ENTRIES(m) \
> + ((__u32)(sizeof(*(m)->max_entries) / sizeof(**(m)->max_entries)))
> +
> +#ifndef bpf_tail_call_static
> +#define bpf_tail_call_static(ctx, map, slot) \
> +({ \
> + /* wrapped to avoid double evaluation. */ \
> + const __u32 __slot = (slot); \
> + __bpf_tail_call_warn(__slot >= BPF_MAP_ENTRIES(map)); \
> + /* Avoid re-expand & invoke original as (bpf_tail_call_static)(..) */ \
> + (bpf_tail_call_static)(ctx, map, __slot); \
> +})
> +#endif /* bpf_tail_call_static */
> +#endif
> +
> #endif
> #endif
I got compilation failures with llvm21.
In file included from progs/bpf_flow.c:19:
/home/yhs/work/bpf-next/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:178:29: error: function '__bpf_tail_call_warn' has internal
linkage but is not defined [-Werror,-Wundefined-internal]
178 | static __always_inline void __bpf_tail_call_warn(int oob)
| CLNG-BPF [test_progs] btf_type_tag_percpu.bpf.o
^
progs/bpf_flow.c:122:3: note: used here
122 | bpf_tail_call_static(skb, &jmp_table, IP);
| ^
/home/yhs/work/bpf-next/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:189:2: note: expanded from macro 'bpf_tail_call_static'
189 | __bpf_tail_c CLNG-BPF [test_progs] btf_type_tag_user.bpf.o
all_warn(__slot >= BPF_MAP_ENTRIES(map)); CLNG-BPF [test_progs] cb_refs.bpf.o
\
| ^
>
> --
> 2.51.0
prev parent reply other threads:[~2025-09-05 4:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 2:53 [RFC bpf-next 0/1] " Hoyeon Lee
2025-09-05 2:53 ` [RFC bpf-next 1/1] " Hoyeon Lee
2025-09-05 4:00 ` Yonghong Song [this message]
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=6b52caf8-51f0-45ed-8f59-11f24dd2861e@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hoyeon.lee@suse.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=sdf@fomichev.me \
--cc=song@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
all inboxes | Powered by JetHome®