From: patchwork-bot+netdevbpf@kernel.org
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, kernel-team@fb.com,
mykolal@fb.com
Subject: Re: [PATCH bpf] selftests/bpf: fix stacktrace_build_id with missing kprobe/urandom_read
Date: Fri, 27 May 2022 15:10:11 +0000 [thread overview]
Message-ID: <165366421191.28804.10243668813609197004.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220526191608.2364049-1-song@kernel.org>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 26 May 2022 12:16:08 -0700 you wrote:
> Kernel function urandom_read is replaced with urandom_read_iter.
> Therefore, kprobe on urandom_read is not working any more:
>
> [root@eth50-1 bpf]# ./test_progs -n 161
> test_stacktrace_build_id:PASS:skel_open_and_load 0 nsec
> libbpf: kprobe perf_event_open() failed: No such file or directory
> libbpf: prog 'oncpu': failed to create kprobe 'urandom_read+0x0' \
> perf event: No such file or directory
> libbpf: prog 'oncpu': failed to auto-attach: -2
> test_stacktrace_build_id:FAIL:attach_tp err -2
> 161 stacktrace_build_id:FAIL
>
> [...]
Here is the summary with links:
- [bpf] selftests/bpf: fix stacktrace_build_id with missing kprobe/urandom_read
https://git.kernel.org/bpf/bpf/c/59ed76fe2f98
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:[~2022-05-27 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 19:16 [PATCH bpf] selftests/bpf: fix stacktrace_build_id with missing kprobe/urandom_read Song Liu
2022-05-26 19:28 ` David Vernet
2022-05-27 15:10 ` 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=165366421191.28804.10243668813609197004.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=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=song@kernel.org \
/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