BPF List
 help / color / mirror / Atom feed
From: Hou Tao <houtao@huaweicloud.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>, bpf@vger.kernel.org
Cc: daniel@iogearbox.net, andrii@kernel.org, martin.lau@kernel.org,
	memxor@gmail.com, eddyz87@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next] bpf: Fix deadlock between rcu_tasks_trace and event_mutex.
Date: Tue, 25 Feb 2025 21:03:38 +0800	[thread overview]
Message-ID: <df335e68-2b30-7cd3-1fb4-e988c8d8ff82@huaweicloud.com> (raw)
In-Reply-To: <20250224221637.4780-1-alexei.starovoitov@gmail.com>

Hi,

On 2/25/2025 6:16 AM, Alexei Starovoitov wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> Fix the following deadlock:
> CPU A
> _free_event()
>   perf_kprobe_destroy()
>     mutex_lock(&event_mutex)
>       perf_trace_event_unreg()
>         synchronize_rcu_tasks_trace()
>
> There are several paths where _free_event() grabs event_mutex
> and calls sync_rcu_tasks_trace. Above is one such case.
>
> CPU B
> bpf_prog_test_run_syscall()
>   rcu_read_lock_trace()
>     bpf_prog_run_pin_on_cpu()
>       bpf_prog_load()
>         bpf_tracing_func_proto()
>           trace_set_clr_event()
>             mutex_lock(&event_mutex)

Considering the unregistered case is not so frequency, would it better
to use mutex_trylock firstly, then fallback to workqueue when the
event_mutex is busy ?
>
> Delegate trace_set_clr_event() to workqueue to avoid
> such lock dependency.
>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> ---
>  kernel/trace/bpf_trace.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
> index a612f6f182e5..13bef2462e94 100644
> --- a/kernel/trace/bpf_trace.c
> +++ b/kernel/trace/bpf_trace.c
> @@ -392,7 +392,7 @@ static const struct bpf_func_proto bpf_trace_printk_proto = {
>  	.arg2_type	= ARG_CONST_SIZE,
>  };
>  
> -static void __set_printk_clr_event(void)
> +static void __set_printk_clr_event(struct work_struct *work)
>  {
>  	/*
>  	 * This program might be calling bpf_trace_printk,
> @@ -405,10 +405,11 @@ static void __set_printk_clr_event(void)
>  	if (trace_set_clr_event("bpf_trace", "bpf_trace_printk", 1))
>  		pr_warn_ratelimited("could not enable bpf_trace_printk events");
>  }
> +static DECLARE_WORK(set_printk_work, __set_printk_clr_event);
>  
>  const struct bpf_func_proto *bpf_get_trace_printk_proto(void)
>  {
> -	__set_printk_clr_event();
> +	schedule_work(&set_printk_work);
>  	return &bpf_trace_printk_proto;
>  }
>  
> @@ -451,7 +452,7 @@ static const struct bpf_func_proto bpf_trace_vprintk_proto = {
>  
>  const struct bpf_func_proto *bpf_get_trace_vprintk_proto(void)
>  {
> -	__set_printk_clr_event();
> +	schedule_work(&set_printk_work);
>  	return &bpf_trace_vprintk_proto;
>  }
>  


  parent reply	other threads:[~2025-02-25 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 22:16 [PATCH bpf-next] bpf: Fix deadlock between rcu_tasks_trace and event_mutex Alexei Starovoitov
2025-02-25  1:06 ` Andrii Nakryiko
2025-02-25  1:56   ` Alexei Starovoitov
2025-02-25 13:03 ` Hou Tao [this message]
2025-02-25 16:01   ` Alexei Starovoitov
2025-02-26 17:00 ` 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=df335e68-2b30-7cd3-1fb4-e988c8d8ff82@huaweicloud.com \
    --to=houtao@huaweicloud.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.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