From: KaFai Wan <kafai.wan@linux.dev>
To: patchwork-bot+netdevbpf@kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
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,
shuah@kernel.org, nathan@kernel.org, ndesaulniers@google.com,
morbo@google.com, justinstitt@google.com,
donggeunyoo.kernel@gmail.com, leon.hwang@linux.dev,
menglong8.dong@gmail.com, yatsenko@meta.com,
jiangfeng@kylinos.cn, bjorn@kernel.org, puranjay@kernel.org,
vineet.gupta@linux.dev, mykolal@fb.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH bpf-next v2 0/7] selftests/bpf: Fix selftests failures with LLVM 23
Date: Sat, 17 Oct 2026 08:57:18 +0800 [thread overview]
Message-ID: <f77fd2b8bce1a029ac295b4482402a8c2203db57.camel@linux.dev> (raw)
In-Reply-To: <179211120751.4176565.4973025143783418812.git-patchwork-notify@kernel.org>
On Fri, 2026-10-16 at 00:40 +0000, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
>
> This series was applied to bpf/bpf-next.git (master)
> by Alexei Starovoitov <ast@kernel.org>:
>
> 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.
--
Thanks,
KaFai
prev parent reply other threads:[~2026-10-17 0:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 11:30 [PATCH bpf-next v2 0/7] selftests/bpf: Fix selftests failures with LLVM 23 KaFai Wan
2026-10-14 11:30 ` [PATCH bpf-next v2 1/7] bpf: Determine freplace staticness from BTF linkage KaFai Wan
2026-10-14 11:30 ` [PATCH bpf-next v2 2/7] selftests/bpf: Fix stack_arg precision backtracking log expectation KaFai Wan
2026-10-14 11:30 ` [PATCH bpf-next v2 3/7] selftests/bpf: Fix stack arg pruning test JOIN " KaFai Wan
2026-10-14 11:30 ` [PATCH bpf-next v2 4/7] selftests/bpf: Use _exit() in uprobe_multi_test clone-ed child KaFai Wan
2026-10-14 11:30 ` [PATCH bpf-next v2 5/7] selftests/bpf: Fix prog_tests framework subtest count checks KaFai Wan
2026-10-14 11:30 ` [PATCH bpf-next v2 6/7] selftests/bpf: Skip expected_msgs subtests when stdout is not saved KaFai Wan
2026-10-14 12:08 ` bot+bpf-ci
2026-10-14 15:41 ` KaFai Wan
2026-10-14 11:30 ` [PATCH bpf-next v2 7/7] selftests/bpf: Skip compare_text subtest " KaFai Wan
2026-10-14 12:08 ` bot+bpf-ci
2026-10-14 16:20 ` KaFai Wan
2026-10-16 0:40 ` [PATCH bpf-next v2 0/7] selftests/bpf: Fix selftests failures with LLVM 23 patchwork-bot+netdevbpf
2026-10-17 0:57 ` KaFai Wan [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=f77fd2b8bce1a029ac295b4482402a8c2203db57.camel@linux.dev \
--to=kafai.wan@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=donggeunyoo.kernel@gmail.com \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jiangfeng@kylinos.cn \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=menglong8.dong@gmail.com \
--cc=morbo@google.com \
--cc=mykolal@fb.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=puranjay@kernel.org \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=vineet.gupta@linux.dev \
--cc=yatsenko@meta.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.