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] bpf: Fix a few selftest failures due to llvm18 change
Date: Mon, 27 Nov 2023 14:00:23 +0000 [thread overview]
Message-ID: <170109362395.30312.3689958762072528759.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231127050342.1945270-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sun, 26 Nov 2023 21:03:42 -0800 you wrote:
> With latest upstream llvm18, the following test cases failed:
> $ ./test_progs -j
> #13/2 bpf_cookie/multi_kprobe_link_api:FAIL
> #13/3 bpf_cookie/multi_kprobe_attach_api:FAIL
> #13 bpf_cookie:FAIL
> #77 fentry_fexit:FAIL
> #78/1 fentry_test/fentry:FAIL
> #78 fentry_test:FAIL
> #82/1 fexit_test/fexit:FAIL
> #82 fexit_test:FAIL
> #112/1 kprobe_multi_test/skel_api:FAIL
> #112/2 kprobe_multi_test/link_api_addrs:FAIL
> ...
> #112 kprobe_multi_test:FAIL
> #356/17 test_global_funcs/global_func17:FAIL
> #356 test_global_funcs:FAIL
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Fix a few selftest failures due to llvm18 change
https://git.kernel.org/bpf/bpf-next/c/b16904fd9f01
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-11-27 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 5:03 [PATCH bpf-next] bpf: Fix a few selftest failures due to llvm18 change Yonghong Song
2023-11-27 14:00 ` patchwork-bot+netdevbpf [this message]
2023-11-27 18:49 ` Andrii Nakryiko
2023-11-27 19:49 ` Yonghong Song
2023-11-27 19:57 ` Andrii Nakryiko
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=170109362395.30312.3689958762072528759.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