From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Menglong Dong <menglong8.dong@gmail.com>,
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 v2 1/2] tracing: fgraph: Protect return handler from recursion loop
Date: Sat, 27 Sep 2025 08:57:53 -0400 [thread overview]
Message-ID: <20250927085753.02b55a18@batman.local.home> (raw)
In-Reply-To: <20250925032611.52475590@batman.local.home>
On Thu, 25 Sep 2025 03:26:11 -0400
Steven Rostedt <rostedt@kernel.org> wrote:
> On Thu, 25 Sep 2025 00:34:10 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
>
> > Hi Steve,
> >
> > Can you pick this ? Or I will do?
>
> I'll take it. I'm currently pulling in patches now anyway. Although,
> while I'm traveling, I'm a bit slow at it.
>
Masami, you didn't include linux-trace-kernel mailing list, so it's not in patchwork.
Can you please resend?
-- Steve
next prev parent reply other threads:[~2025-09-27 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 6:35 [PATCH v2 0/2] tracing: fprobe: " Masami Hiramatsu (Google)
2025-09-22 6:35 ` [PATCH v2 1/2] tracing: fgraph: " 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 [this message]
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=20250927085753.02b55a18@batman.local.home \
--to=rostedt@goodmis.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=mhiramat@kernel.org \
--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
all inboxes | Powered by JetHome®