public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: peterz@infradead.org, jolsa@kernel.org, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com, kees@kernel.org,
	samitolvanen@google.com, rppt@kernel.org, luto@kernel.org,
	ast@kernel.org, andrii@kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH] x86/ibt: make is_endbr() notrace
Date: Fri, 19 Sep 2025 21:32:55 +0900	[thread overview]
Message-ID: <20250919213255.db643846f6dddfe409f03e55@kernel.org> (raw)
In-Reply-To: <5925436.DvuYhMxLoT@7940hx>

On Fri, 19 Sep 2025 16:58:57 +0800
Menglong Dong <menglong8.dong@gmail.com> wrote:

> On 2025/9/19 16:52 Masami Hiramatsu <mhiramat@kernel.org> write:
> > On Thu, 18 Sep 2025 20:09:39 +0800
> > Menglong Dong <menglong8.dong@gmail.com> wrote:
> > 
> > > is_endbr() is called in __ftrace_return_to_handler -> fprobe_return ->
> > > kprobe_multi_link_exit_handler -> is_endbr.
> > > 
> > > It is not protected by the "bpf_prog_active", so it can't be traced by
> > > kprobe-multi, which can cause recurring and panic the kernel. Fix it by
> > > make it notrace.
> > 
> > Ah, OK. This is fprobe's issue. fprobe depends on fgraph to check
> > recursion, but fgraph only detects the recursion in the entry handler.
> > Thus it happens in the exit handler, fprobe does not check the recursion.
> > 
> > But since the fprobe provides users to register callback at exit, it
> > should check the recursion in return path too.
> 
> That's a good idea to provide recursion checking for the exit handler,
> which is able to solve this problem too.
> 
> If so, we don't need to check the recursion on the kprobe-multi anymore.
> Do we?

Yes, but *if possible*, please avoid calling such functions from fprobe
callbacks. This just prevents kernel crash from such recursion, but that
means it is not possible to trace such functions.

Thank you,


> 
> Thanks!
> Menglong Dong
> 
> > 
> > Thanks,
> > 
> > -- 
> > Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > 
> 
> 
> 
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2025-09-19 12:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18 12:09 [PATCH] x86/ibt: make is_endbr() notrace Menglong Dong
2025-09-18 13:05 ` Peter Zijlstra
2025-09-18 13:32   ` Menglong Dong
2025-09-18 16:02     ` Alexei Starovoitov
2025-09-18 16:59       ` Peter Zijlstra
2025-09-18 17:53         ` Alexei Starovoitov
2025-09-19  1:13           ` Menglong Dong
2025-09-22  6:52             ` Peter Zijlstra
2025-09-22  7:13               ` menglong.dong
2025-09-22  7:19                 ` Peter Zijlstra
2025-09-22  7:21                   ` Menglong Dong
2025-09-22  6:36           ` Peter Zijlstra
2025-09-18 16:56     ` Peter Zijlstra
2025-09-19 12:35       ` Masami Hiramatsu
2025-09-19  8:52 ` Masami Hiramatsu
2025-09-19  8:58   ` Menglong Dong
2025-09-19 12:32     ` Masami Hiramatsu [this message]
2025-09-19 11:57 ` [PATCH] tracing: fgraph: Protect return handler from recursion loop Masami Hiramatsu (Google)
2025-09-19 15:27   ` Steven Rostedt
2025-09-20  7:45     ` Jiri Olsa
2025-09-22  6:16       ` Masami Hiramatsu
2025-09-22 13:38         ` Jiri Olsa
2025-09-22 14:42           ` Steven Rostedt
2025-09-22 19:45           ` Jiri Olsa
2025-09-21  4:05     ` Masami Hiramatsu
2025-09-21 22:52       ` Steven Rostedt
2025-09-24 22:58         ` Masami Hiramatsu
2025-09-20 13:39   ` Menglong Dong
2025-09-21  4:06     ` Masami Hiramatsu
2025-09-21 23:00       ` Steven Rostedt
2025-09-24 22:59         ` Masami Hiramatsu
2025-09-22  5:19     ` Masami Hiramatsu

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=20250919213255.db643846f6dddfe409f03e55@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bp@alien8.de \
    --cc=bpf@vger.kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=menglong8.dong@gmail.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rppt@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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