From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
sdf@google.com, haoluo@google.com
Subject: Re: [PATCH bpf 1/2] selftests/bpf: Filter out default_idle from kprobe_multi bench
Date: Mon, 21 Nov 2022 20:00:17 +0000 [thread overview]
Message-ID: <166906081704.30865.17096709032712849475.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221116100228.2064612-1-jolsa@kernel.org>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 16 Nov 2022 11:02:27 +0100 you wrote:
> Alexei hit following rcu warning when running prog_test -j.
>
> [ 128.049567] WARNING: suspicious RCU usage
> [ 128.049569] 6.1.0-rc2 #912 Tainted: G O
> ...
> [ 128.050944] kprobe_multi_link_handler+0x6c/0x1d0
> [ 128.050947] ? kprobe_multi_link_handler+0x42/0x1d0
> [ 128.050950] ? __cpuidle_text_start+0x8/0x8
> [ 128.050952] ? __cpuidle_text_start+0x8/0x8
> [ 128.050958] fprobe_handler.part.1+0xac/0x150
> [ 128.050964] 0xffffffffa02130c8
> [ 128.050991] ? default_idle+0x5/0x20
> [ 128.050998] default_idle+0x5/0x20
>
> [...]
Here is the summary with links:
- [bpf,1/2] selftests/bpf: Filter out default_idle from kprobe_multi bench
https://git.kernel.org/bpf/bpf/c/2b506f20af2b
- [bpf,2/2] selftests/bpf: Make test_bench_attach serial
https://git.kernel.org/bpf/bpf/c/8be602dadb2f
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-11-21 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 10:02 [PATCH bpf 1/2] selftests/bpf: Filter out default_idle from kprobe_multi bench Jiri Olsa
2022-11-16 10:02 ` [PATCH bpf 2/2] selftests/bpf: Make test_bench_attach serial Jiri Olsa
2022-11-21 19:57 ` [PATCH bpf 1/2] selftests/bpf: Filter out default_idle from kprobe_multi bench Alexei Starovoitov
2022-11-21 20: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=166906081704.30865.17096709032712849475.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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