From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: Saket Kumar Bhaskar <skb99@linux.ibm.com>,
Hari Bathini <hbathini@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
bpf <bpf@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [mainline][bpf] build failure: conflicting bpf_arena_* prototypes between vmlinux.h and bpf_arena_common.h
Date: Mon, 4 May 2026 14:12:17 +0530 [thread overview]
Message-ID: <362eaba2-54dd-4b59-81f5-65abb916e916@linux.ibm.com> (raw)
Greetings!!!
I’m seeing a CLANG-BPF build failure in tools/testing/selftests/bpf
related to conflicting prototypes of bpf_arena_* helpers between
vmlinux.h and bpf_arena_common.h, on mainline kernel.
Error log:
In file included from progs/arena_strsearch.c:12:
In file included from
tools/testing/selftests/bpf/bpf_arena_strsearch.h:4:
tools/testing/selftests/bpf/bpf_arena_common.h:47:15:
error: conflicting types for 'bpf_arena_alloc_pages'
void __arena* bpf_arena_alloc_pages(void *map,
void __arena *addr,
__u32 page_cnt,
__u32 node_id,
__u64 flags);
tools/testing/selftests/bpf/tools/include/vmlinux.h:135295:14:
note: previous declaration is here
extern void *bpf_arena_alloc_pages(void *p__map,
void *addr__ign,
u32 page_cnt,
int node_id,
u64 flags) __weak __ksym;
tools/testing/selftests/bpf/bpf_arena_common.h:49:5:
error: conflicting types for 'bpf_arena_reserve_pages'
int bpf_arena_reserve_pages(void *map,
void __arena *addr,
__u32 page_cnt) __ksym __weak;
tools/testing/selftests/bpf/tools/include/vmlinux.h:135297:12:
note: previous declaration is here
extern int bpf_arena_reserve_pages(void *p__map,
void *ptr__ign,
u32 page_cnt) __weak __ksym;
tools/testing/selftests/bpf/bpf_arena_common.h:50:6:
error: conflicting types for 'bpf_arena_free_pages'
void bpf_arena_free_pages(void *map,
void __arena *ptr,
__u32 page_cnt) __ksym __weak;
tools/testing/selftests/bpf/tools/include/vmlinux.h:135296:13:
note: previous declaration is here
extern void bpf_arena_free_pages(void *p__map,
void *ptr__ign,
u32 page_cnt) __weak __ksym;
Tool chain Versions:
gcc (GCC) 14.2.0
# clang --version
clang version 23.0.0git (https://github.com/llvm/llvm-project.git
bd6bfba3e50343c112a04b639394ab85be17c29b)
# llc --version
LLVM (http://llvm.org/):
LLVM version 23.0.0git
Optimized build.
Default target: powerpc64le-unknown-linux-gnu
Host CPU: (unknown)
Registered Targets:
bpf - BPF (host endian)
bpfeb - BPF (big endian)
bpfel - BPF (little endian)
ppc32 - PowerPC 32
ppc32le - PowerPC 32 LE
ppc64 - PowerPC 64
ppc64le - PowerPC 64 LE
# objcopy --version | head -1
GNU objcopy version 2.35.2-67.el9_7.1
# ld --version | head -1
GNU ld version 2.35.2-67.el9_7.1
If you happen to fix this, please add below tag.
Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Regards,
Venkat.
next reply other threads:[~2026-05-04 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 8:42 Venkat Rao Bagalkote [this message]
2026-05-04 8:44 ` [mainline][bpf] build failure: conflicting bpf_arena_* prototypes between vmlinux.h and bpf_arena_common.h 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=362eaba2-54dd-4b59-81f5-65abb916e916@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=hbathini@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=skb99@linux.ibm.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