BPF List
 help / color / mirror / Atom feed
From: Tao Chen <chen.dylane@linux.dev>
To: Yonghong Song <yonghong.song@linux.dev>, Jiri Olsa <olsajiri@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
	haoluo@google.com, mattbobrowski@google.com, rostedt@goodmis.org,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: Disable migrate when kprobe_multi attach to access bpf_prog_active
Date: Tue, 5 Aug 2025 20:28:48 +0800	[thread overview]
Message-ID: <6a931aca-1aad-41e4-8449-89f48121abba@linux.dev> (raw)
In-Reply-To: <3cf22505-e338-4cc1-ab76-896bfc336b40@linux.dev>

在 2025/8/5 12:05, Yonghong Song 写道:
> 
> 
> On 8/4/25 6:02 AM, Jiri Olsa wrote:
>> On Mon, Aug 04, 2025 at 08:16:15PM +0800, Tao Chen wrote:
>>> The syscall link_create not protected by bpf_disable_instrumentation,
>>> accessing percpu data bpf_prog_active should use cpu local_lock when
>>> kprobe_multi program attach.
>>>
>>> Fixes: 0dcac2725406 ("bpf: Add multi kprobe link")
>>> Signed-off-by: Tao Chen <chen.dylane@linux.dev>
>>> ---
>>>   kernel/trace/bpf_trace.c | 4 ++--
>>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
>>> index 3ae52978cae..f6762552e8e 100644
>>> --- a/kernel/trace/bpf_trace.c
>>> +++ b/kernel/trace/bpf_trace.c
>>> @@ -2728,23 +2728,23 @@ kprobe_multi_link_prog_run(struct 
>>> bpf_kprobe_multi_link *link,
>>>       struct pt_regs *regs;
>>>       int err;
>>> +    migrate_disable();
>>>       if (unlikely(__this_cpu_inc_return(bpf_prog_active) != 1)) {
>> this is called all the way from graph tracer, which disables 
>> preemption in
>> function_graph_enter_regs, so I think we can safely use 
>> __this_cpu_inc_return
> 
> Agree. migrate_disable() is not needed here. But it would be great to 
> add some
> comments here since for most other prog_run, they typically have 
> migrate_disable/enable.
> 
>>
>>
>>>           bpf_prog_inc_misses_counter(link->link.prog);
>>>           err = 1;
>>>           goto out;
>>>       }
>>> -    migrate_disable();
>> hum, but now I'm not sure why we disable migration in here then
> 
> Probably a oversight.
> 
>>
>> jirka
>>
>>>       rcu_read_lock();
>>>       regs = ftrace_partial_regs(fregs, bpf_kprobe_multi_pt_regs_ptr());
>>>       old_run_ctx = bpf_set_run_ctx(&run_ctx.session_ctx.run_ctx);
>>>       err = bpf_prog_run(link->link.prog, regs);
>>>       bpf_reset_run_ctx(old_run_ctx);
>>>       rcu_read_unlock();
>>> -    migrate_enable();
>>>    out:
>>>       __this_cpu_dec(bpf_prog_active);
>>> +    migrate_enable();
>>>       return err;
>>>   }
>>> -- 
>>> 2.48.1
>>>
> 

Hi Jiri, Yonghong,

I send another patch as you suggested, pls review it, thanks.

https://lore.kernel.org/bpf/20250805122312.1890951-1-chen.dylane@linux.dev

-- 
Best Regards
Tao Chen

      reply	other threads:[~2025-08-05 12:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 12:16 [PATCH bpf-next] bpf: Disable migrate when kprobe_multi attach to access bpf_prog_active Tao Chen
2025-08-04 13:02 ` Jiri Olsa
2025-08-04 14:15   ` Tao Chen
2025-08-05  9:07     ` Jiri Olsa
2025-08-05  9:27       ` Tao Chen
2025-08-05  4:05   ` Yonghong Song
2025-08-05 12:28     ` Tao Chen [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=6a931aca-1aad-41e4-8449-89f48121abba@linux.dev \
    --to=chen.dylane@linux.dev \
    --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=john.fastabend@gmail.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mattbobrowski@google.com \
    --cc=mhiramat@kernel.org \
    --cc=olsajiri@gmail.com \
    --cc=rostedt@goodmis.org \
    --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