From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
syzbot+2e0d2840414ce817aaac@syzkaller.appspotmail.com,
bpf@vger.kernel.org, linux-perf-users@vger.kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@chromium.org, sdf@fomichev.me,
haoluo@google.com, sean@mess.org, peterz@infradead.org
Subject: Re: [PATCH bpf] bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog
Date: Tue, 10 Dec 2024 18:30:30 +0000 [thread overview]
Message-ID: <173385543052.937529.3035278335485000200.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241208142507.1207698-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sun, 8 Dec 2024 15:25:07 +0100 you wrote:
> Syzbot reported [1] crash that happens for following tracing scenario:
>
> - create tracepoint perf event with attr.inherit=1, attach it to the
> process and set bpf program to it
> - attached process forks -> chid creates inherited event
>
> the new child event shares the parent's bpf program and tp_event
> (hence prog_array) which is global for tracepoint
>
> [...]
Here is the summary with links:
- [bpf] bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog
https://git.kernel.org/bpf/bpf/c/978c4486cca5
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:[~2024-12-10 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-08 14:25 [PATCH bpf] bpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog Jiri Olsa
2024-12-10 18:30 ` 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=173385543052.937529.3035278335485000200.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=linux-perf-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sdf@fomichev.me \
--cc=sean@mess.org \
--cc=songliubraving@fb.com \
--cc=syzbot+2e0d2840414ce817aaac@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