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 v4] bpf: Fix test verif_scale_strobemeta_subprogs failure due to llvm19
Date: Thu, 15 Feb 2024 22:00:29 +0000 [thread overview]
Message-ID: <170803442900.22703.11941141637840510871.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240214232951.4113094-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 14 Feb 2024 15:29:51 -0800 you wrote:
> With latest llvm19, I hit the following selftest failures with
>
> $ ./test_progs -j
> libbpf: prog 'on_event': BPF program load failed: Permission denied
> libbpf: prog 'on_event': -- BEGIN PROG LOAD LOG --
> combined stack size of 4 calls is 544. Too large
> verification time 1344153 usec
> stack depth 24+440+0+32
> processed 51008 insns (limit 1000000) max_states_per_insn 19 total_states 1467 peak_states 303 mark_read 146
> -- END PROG LOAD LOG --
> libbpf: prog 'on_event': failed to load: -13
> libbpf: failed to load object 'strobemeta_subprogs.bpf.o'
> scale_test:FAIL:expect_success unexpected error: -13 (errno 13)
> #498 verif_scale_strobemeta_subprogs:FAIL
>
> [...]
Here is the summary with links:
- [bpf-next,v4] bpf: Fix test verif_scale_strobemeta_subprogs failure due to llvm19
https://git.kernel.org/bpf/bpf-next/c/682158ab532a
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:[~2024-02-15 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 23:29 [PATCH bpf-next v4] bpf: Fix test verif_scale_strobemeta_subprogs failure due to llvm19 Yonghong Song
2024-02-15 22:00 ` 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=170803442900.22703.11941141637840510871.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