From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@kernel.org>,
Menglong Dong <menglong8.dong@gmail.com>
Cc: 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, mhiramat@kernel.org,
ast@kernel.org, andrii@kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: [PATCH v2 0/2] tracing: fprobe: Protect return handler from recursion loop
Date: Mon, 22 Sep 2025 15:35:11 +0900 [thread overview]
Message-ID: <175852291163.307379.14414635977719513326.stgit@devnote2> (raw)
The following series fixes a recursive loop issue on fprobe by adding
ftrace_test_recursion_trylock() in __ftrace_return_to_handler().
The previous version is here;
https://lore.kernel.org/all/175828305637.117978.4183947592750468265.stgit@devnote2/
This v2 removes WARN_ON from __ftrace_return_to_handler() and adds
kunit test cases for recursive call [2/2].
---
Masami Hiramatsu (Google) (2):
tracing: fgraph: Protect return handler from recursion loop
lib/test_fprobe: Add recursion check test cases
kernel/trace/fgraph.c | 12 ++++++
lib/tests/test_fprobe.c | 92 ++++++++++++++++++++++++++++++++++++++++++++++-
2 files changed, 102 insertions(+), 2 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2025-09-22 6:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 6:35 Masami Hiramatsu (Google) [this message]
2025-09-22 6:35 ` [PATCH v2 1/2] tracing: fgraph: Protect return handler from recursion loop Masami Hiramatsu (Google)
2025-09-22 8:01 ` menglong.dong
2025-09-24 15:34 ` Masami Hiramatsu
2025-09-25 7:26 ` Steven Rostedt
2025-09-27 12:57 ` Steven Rostedt
2025-09-28 12:56 ` Steven Rostedt
2025-09-29 0:02 ` Masami Hiramatsu
2025-09-22 6:35 ` [PATCH v2 2/2] lib/test_fprobe: Add recursion check test cases Masami Hiramatsu (Google)
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=175852291163.307379.14414635977719513326.stgit@devnote2 \
--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=rostedt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.