Re: [PATCH bpf-next v2 0/7] selftests/bpf: Fix selftests failures with LLVM 23
From: Alexei Starovoitov
Date: Sat Oct 17 2026 - 20:41:06 EST
On Sat Oct 17, 2026 at 12:57 AM UTC, KaFai Wan wrote:
> On Fri, 2026-10-16 at 00:40 +0000, patchwork-bot+netdevbpf@xxxxxxxxxx wrote:
>> Hello:
>>
>> This series was applied to bpf/bpf-next.git (master)
>> by Alexei Starovoitov <ast@xxxxxxxxxx>:
>>
>> On Wed, 14 Oct 2026 19:30:36 +0800 you wrote:
>> > Building with clang/LLVM 23 breaks several selftests. Patches #1 to #4 fix
>> > those failures.
>> >
>> > The following self-tests also fail under specific invocations of
>> > test_progs:
>> >
>> > - ./test_progs -t prog_tests_framework/test_fail -v
>> > test_prog_tests_framework:FAIL:skip_cnt_check
>> > unexpected skip_cnt_check: actual 0 != expected 2
>> >
>> > [...]
>>
>> Here is the summary with links:
>> - [bpf-next,v2,1/7] bpf: Determine freplace staticness from BTF linkage
>> (no matching commit)
>> - [bpf-next,v2,2/7] selftests/bpf: Fix stack_arg precision backtracking log expectation
>> (no matching commit)
>> - [bpf-next,v2,3/7] selftests/bpf: Fix stack arg pruning test JOIN log expectation
>> (no matching commit)
>> - [bpf-next,v2,4/7] selftests/bpf: Use _exit() in uprobe_multi_test clone-ed child
>> (no matching commit)
>> - [bpf-next,v2,5/7] selftests/bpf: Fix prog_tests framework subtest count checks
>> https://git.kernel.org/bpf/bpf-next/c/c87652656a55
>> - [bpf-next,v2,6/7] selftests/bpf: Skip expected_msgs subtests when stdout is not saved
>> https://git.kernel.org/bpf/bpf-next/c/cc4b1c161d92
>> - [bpf-next,v2,7/7] selftests/bpf: Skip compare_text subtest when stdout is not saved
>> https://git.kernel.org/bpf/bpf-next/c/7ebf808caa76
>>
>> You are awesome, thank you!
>
> Hi Alexei,
>
> I resent the last 3 patches in v2 and changed the subject, expecting v2 to be reviewed first so we
> could skip v1. Sorry, it didn’t work. The bot closed this thread while applying the 3 patches from
> v1. Should I resend the first 4 patches?
>
> Sorry for the inconvenience.
Sorry. My fault.
Pls resend. It will be easier on bots.