From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/7] tracing: probe: Allocate traceprobe_parse_context from heap
Date: Wed, 23 Jul 2025 09:26:48 +0900 [thread overview]
Message-ID: <20250723092648.3fc87e0fff6abb04a7234a15@kernel.org> (raw)
In-Reply-To: <20250722183813.74dd1386@gandalf.local.home>
On Tue, 22 Jul 2025 18:38:13 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 23 Jul 2025 07:01:46 +0900
> "Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
>
> > From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> >
> > Instead of allocating traceprobe_parse_context on stack, allocate it
> > dynamically from heap (slab).
> >
> > This change is likely intended to prevent potential stack overflow
> > issues, which can be a concern in the kernel environment where stack
> > space is limited.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202506240416.nZIhDXoO-lkp@intel.com/
> > Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
>
Thanks!
> -- Steve
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-07-23 0:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 22:01 [PATCH v3 0/7] tracing: probes: Use heap instead of stack for temporary buffers Masami Hiramatsu (Google)
2025-07-22 22:01 ` [PATCH v3 1/7] tracing: probes: Sort #include alphabetically Masami Hiramatsu (Google)
2025-07-22 22:01 ` [PATCH v3 2/7] tracing: probe: Allocate traceprobe_parse_context from heap Masami Hiramatsu (Google)
2025-07-22 22:38 ` Steven Rostedt
2025-07-23 0:26 ` Masami Hiramatsu [this message]
2025-07-22 22:01 ` [PATCH v3 3/7] tracing: fprobe-event: Allocate string buffers " Masami Hiramatsu (Google)
2025-07-22 22:40 ` Steven Rostedt
2025-07-22 22:02 ` [PATCH v3 4/7] tracing: kprobe-event: " Masami Hiramatsu (Google)
2025-07-22 22:02 ` [PATCH v3 5/7] tracing: eprobe-event: " Masami Hiramatsu (Google)
2025-07-22 22:02 ` [PATCH v3 6/7] tracing: uprobe-event: " Masami Hiramatsu (Google)
2025-07-22 22:42 ` Steven Rostedt
2025-07-22 22:02 ` [PATCH v3 7/7] tracing: probes: Add a kerneldoc for traceprobe_parse_event_name() Masami Hiramatsu (Google)
2025-07-22 22:44 ` Steven Rostedt
2025-07-23 0:29 ` 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=20250723092648.3fc87e0fff6abb04a7234a15@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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
Powered by JetHome