From: patchwork-bot+netdevbpf@kernel.org
To: Vineet Gupta <vineet.gupta@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
john.fastabend@gmail.com, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
jose.marchesi@oracle.com, david.faust@oss.qualcomm.com
Subject: Re: [PATCH bpf-next v4 0/8] selftests/bpf: let the arena tests build with GCC
Date: Tue, 03 Nov 2026 21:20:07 +0000 [thread overview]
Message-ID: <179374080755.1885738.6613699311027745325.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261103181816.254686-1-vineet.gupta@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 3 Nov 2026 10:18:08 -0800 you wrote:
> The arena selftests cannot be built by GCC today. Three separate
> build failures stand in the way, and they are all hidden rather than
> avoided by the __BPF_FEATURE_ADDR_SPACE_CAST guards wrapped around
> those tests -- the moment a GCC defines that macro, which is what the
> in-progress arena support does, the guards stop hiding them and the
> build breaks.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/8] selftests/bpf: Build callx tests with GCC that defines __BPF_FEATURE_CALLX
https://git.kernel.org/bpf/bpf-next/c/5b127a2d9d44
- [bpf-next,v4,2/8] selftests/bpf: don't pass clang-only warning flags to GCC
https://git.kernel.org/bpf/bpf-next/c/a74a26a8f284
- [bpf-next,v4,3/8] selftests/bpf: make arena_base() opaque to GCC's -Warray-bounds
https://git.kernel.org/bpf/bpf-next/c/2775ec48ecaa
- [bpf-next,v4,4/8] selftests/bpf: spell the addr_space_cast address spaces in decimal
https://git.kernel.org/bpf/bpf-next/c/0a2eb9a7fa34
- [bpf-next,v4,5/8] selftests/bpf: write the mixed arena/scalar ALU tests in asm
https://git.kernel.org/bpf/bpf-next/c/db06ab42ec4b
- [bpf-next,v4,6/8] selftests/bpf: drop the arena guards and tag the tests that need arena
https://git.kernel.org/bpf/bpf-next/c/84459cc976cd
- [bpf-next,v4,7/8] selftests/bpf: cast explicitly in the struct_ops arena triggers
https://git.kernel.org/bpf/bpf-next/c/7eead323843a
- [bpf-next,v4,8/8] selftests/bpf: cast explicitly in the arena subprog and callback faults
https://git.kernel.org/bpf/bpf-next/c/b64845f6280f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-03 21:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 18:18 Vineet Gupta
2026-11-03 18:18 ` [PATCH bpf-next v4 1/8] selftests/bpf: Build callx tests with GCC that defines __BPF_FEATURE_CALLX Vineet Gupta
2026-11-03 18:18 ` [PATCH bpf-next v4 2/8] selftests/bpf: don't pass clang-only warning flags to GCC Vineet Gupta
2026-11-03 18:18 ` [PATCH bpf-next v4 3/8] selftests/bpf: make arena_base() opaque to GCC's -Warray-bounds Vineet Gupta
2026-11-03 18:18 ` [PATCH bpf-next v4 4/8] selftests/bpf: spell the addr_space_cast address spaces in decimal Vineet Gupta
2026-11-03 18:57 ` bot+bpf-ci
2026-11-03 18:18 ` [PATCH bpf-next v4 5/8] selftests/bpf: write the mixed arena/scalar ALU tests in asm Vineet Gupta
2026-11-03 18:57 ` bot+bpf-ci
2026-11-03 18:18 ` [PATCH bpf-next v4 6/8] selftests/bpf: drop the arena guards and tag the tests that need arena Vineet Gupta
2026-11-03 18:57 ` bot+bpf-ci
2026-11-03 18:18 ` [PATCH bpf-next v4 7/8] selftests/bpf: cast explicitly in the struct_ops arena triggers Vineet Gupta
2026-11-03 18:18 ` [PATCH bpf-next v4 8/8] selftests/bpf: cast explicitly in the arena subprog and callback faults Vineet Gupta
2026-11-03 21:20 ` patchwork-bot+netdevbpf [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=179374080755.1885738.6613699311027745325.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=david.faust@oss.qualcomm.com \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jose.marchesi@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=vineet.gupta@linux.dev \
--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 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®