From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
sdf@google.com,
syzbot+2251879aa068ad9c960d@syzkaller.appspotmail.com,
bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
haoluo@google.com
Subject: Re: [PATCHv2 bpf-next] bpf: Prevent bpf program recursion for raw tracepoint probes
Date: Thu, 22 Sep 2022 01:20:14 +0000 [thread overview]
Message-ID: <166380961483.28833.1573067698902385305.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220916071914.7156-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 16 Sep 2022 09:19:14 +0200 you wrote:
> We got report from sysbot [1] about warnings that were caused by
> bpf program attached to contention_begin raw tracepoint triggering
> the same tracepoint by using bpf_trace_printk helper that takes
> trace_printk_lock lock.
>
> Call Trace:
> <TASK>
> ? trace_event_raw_event_bpf_trace_printk+0x5f/0x90
> bpf_trace_printk+0x2b/0xe0
> bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
> bpf_trace_run2+0x26/0x90
> native_queued_spin_lock_slowpath+0x1c6/0x2b0
> _raw_spin_lock_irqsave+0x44/0x50
> bpf_trace_printk+0x3f/0xe0
> bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
> bpf_trace_run2+0x26/0x90
> native_queued_spin_lock_slowpath+0x1c6/0x2b0
> _raw_spin_lock_irqsave+0x44/0x50
> bpf_trace_printk+0x3f/0xe0
> bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
> bpf_trace_run2+0x26/0x90
> native_queued_spin_lock_slowpath+0x1c6/0x2b0
> _raw_spin_lock_irqsave+0x44/0x50
> bpf_trace_printk+0x3f/0xe0
> bpf_prog_a9aec6167c091eef_prog+0x1f/0x24
> bpf_trace_run2+0x26/0x90
> native_queued_spin_lock_slowpath+0x1c6/0x2b0
> _raw_spin_lock_irqsave+0x44/0x50
> __unfreeze_partials+0x5b/0x160
> ...
>
> [...]
Here is the summary with links:
- [PATCHv2,bpf-next] bpf: Prevent bpf program recursion for raw tracepoint probes
https://git.kernel.org/bpf/bpf-next/c/05b24ff9b2cf
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-09-22 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 7:19 [PATCHv2 bpf-next] bpf: Prevent bpf program recursion for raw tracepoint probes Jiri Olsa
2022-09-22 1:20 ` 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=166380961483.28833.1573067698902385305.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=syzbot+2251879aa068ad9c960d@syzkaller.appspotmail.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