From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix selftest verif_scale_strobemeta failure with llvm22
Date: Sun, 19 Oct 2025 02:30:16 +0000 [thread overview]
Message-ID: <176084101675.3155740.4372204792816827273.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251014051639.1996331-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 13 Oct 2025 22:16:39 -0700 you wrote:
> With latest llvm22, I hit the verif_scale_strobemeta selftest failure
> below:
> $ ./test_progs -n 618
> libbpf: prog 'on_event': BPF program load failed: -E2BIG
> libbpf: prog 'on_event': -- BEGIN PROG LOAD LOG --
> BPF program is too large. Processed 1000001 insn
> verification time 7019091 usec
> stack depth 488
> processed 1000001 insns (limit 1000000) max_states_per_insn 28 total_states 33927 peak_states 12813 mark_read 0
> -- END PROG LOAD LOG --
> libbpf: prog 'on_event': failed to load: -E2BIG
> libbpf: failed to load object 'strobemeta.bpf.o'
> scale_test:FAIL:expect_success unexpected error: -7 (errno 7)
> #618 verif_scale_strobemeta:FAIL
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Fix selftest verif_scale_strobemeta failure with llvm22
https://git.kernel.org/bpf/bpf-next/c/4f8543b5f20f
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:[~2025-10-19 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 5:16 [PATCH bpf-next] selftests/bpf: Fix selftest verif_scale_strobemeta failure with llvm22 Yonghong Song
2025-10-15 16:45 ` Andrii Nakryiko
2025-10-15 19:56 ` Yonghong Song
2025-10-15 20:31 ` Andrii Nakryiko
2025-10-15 20:54 ` Yonghong Song
2025-10-19 2:30 ` 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=176084101675.3155740.4372204792816827273.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=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--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