From: Jiri Olsa <olsajiri@gmail.com>
To: Pu Lehui <pulehui@huaweicloud.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jann Horn <jannh@google.com>, Pu Lehui <pulehui@huawei.com>
Subject: Re: [PATCH bpf-next v2] bpf: Move out synchronize_rcu_tasks_trace from mutex CS
Date: Wed, 8 Jan 2025 12:26:07 +0100 [thread overview]
Message-ID: <Z35gz9q8z7LBNssS@krava> (raw)
In-Reply-To: <20250104013946.1111785-1-pulehui@huaweicloud.com>
On Sat, Jan 04, 2025 at 01:39:46AM +0000, Pu Lehui wrote:
> From: Pu Lehui <pulehui@huawei.com>
>
> Commit ef1b808e3b7c ("bpf: Fix UAF via mismatching bpf_prog/attachment
> RCU flavors") resolved a possible UAF issue in uprobes that attach
> non-sleepable bpf prog by explicitly waiting for a tasks-trace-RCU grace
> period. But, in the current implementation, synchronize_rcu_tasks_trace
> is included within the mutex critical section, which increases the
> length of the critical section and may affect performance. So let's move
> out synchronize_rcu_tasks_trace from mutex CS.
lgtm, adding peter
Reviewed-by: Jiri Olsa <jolsa@kernel.org>
jirka
>
> Signed-off-by: Pu Lehui <pulehui@huawei.com>
> ---
> v2: Simplify code logic. (Jiri)
>
> kernel/trace/bpf_trace.c | 21 +++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
> index 48db147c6c7d..a90880f475af 100644
> --- a/kernel/trace/bpf_trace.c
> +++ b/kernel/trace/bpf_trace.c
> @@ -2245,6 +2245,7 @@ void perf_event_detach_bpf_prog(struct perf_event *event)
> {
> struct bpf_prog_array *old_array;
> struct bpf_prog_array *new_array;
> + struct bpf_prog *prog = NULL;
> int ret;
>
> mutex_lock(&bpf_event_mutex);
> @@ -2265,18 +2266,22 @@ void perf_event_detach_bpf_prog(struct perf_event *event)
> }
>
> put:
> - /*
> - * It could be that the bpf_prog is not sleepable (and will be freed
> - * via normal RCU), but is called from a point that supports sleepable
> - * programs and uses tasks-trace-RCU.
> - */
> - synchronize_rcu_tasks_trace();
> -
> - bpf_prog_put(event->prog);
> + prog = event->prog;
> event->prog = NULL;
>
> unlock:
> mutex_unlock(&bpf_event_mutex);
> +
> + if (prog) {
> + /*
> + * It could be that the bpf_prog is not sleepable (and will be freed
> + * via normal RCU), but is called from a point that supports sleepable
> + * programs and uses tasks-trace-RCU.
> + */
> + synchronize_rcu_tasks_trace();
> +
> + bpf_prog_put(prog);
> + }
> }
>
> int perf_event_query_prog_array(struct perf_event *event, void __user *info)
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2025-01-08 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 1:39 [PATCH bpf-next v2] bpf: Move out synchronize_rcu_tasks_trace from mutex CS Pu Lehui
2025-01-08 11:26 ` Jiri Olsa [this message]
2025-01-08 12:50 ` Peter Zijlstra
2025-01-08 17:50 ` patchwork-bot+netdevbpf
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=Z35gz9q8z7LBNssS@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jannh@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=peterz@infradead.org \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=sdf@fomichev.me \
--cc=song@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