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: Prevent inlining of bpf_fentry_test7()
Date: Wed, 30 Aug 2023 06:48:27 +0000 [thread overview]
Message-ID: <169337810739.20679.14633648454962000249.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230826200843.2210074-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sat, 26 Aug 2023 13:08:43 -0700 you wrote:
> With latest clang18, I hit test_progs failures for the following test:
> #13/2 bpf_cookie/multi_kprobe_link_api:FAIL
> #13/3 bpf_cookie/multi_kprobe_attach_api:FAIL
> #13 bpf_cookie:FAIL
> #75 fentry_fexit:FAIL
> #76/1 fentry_test/fentry:FAIL
> #76 fentry_test:FAIL
> #80/1 fexit_test/fexit:FAIL
> #80 fexit_test:FAIL
> #110/1 kprobe_multi_test/skel_api:FAIL
> #110/2 kprobe_multi_test/link_api_addrs:FAIL
> #110/3 kprobe_multi_test/link_api_syms:FAIL
> #110/4 kprobe_multi_test/attach_api_pattern:FAIL
> #110/5 kprobe_multi_test/attach_api_addrs:FAIL
> #110/6 kprobe_multi_test/attach_api_syms:FAIL
> #110 kprobe_multi_test:FAIL
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Prevent inlining of bpf_fentry_test7()
https://git.kernel.org/bpf/bpf/c/32337c0a2824
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:[~2023-08-30 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 20:08 [PATCH bpf-next] bpf: Prevent inlining of bpf_fentry_test7() Yonghong Song
2023-08-28 0:01 ` Eduard Zingerman
2023-08-28 7:26 ` Alan Maguire
2023-08-29 0:23 ` Yonghong Song
2023-08-30 6:48 ` 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=169337810739.20679.14633648454962000249.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