linux-kernel - [PATCH 0/5] tracing: probes: Use heap instead of stack for temporary buffers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <175283843771.343578.8524137568048302760.stgit@devnote2>
Date: Fri, 18 Jul 2025 20:33:58 +0900
From: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>,
	Masami Hiramatsu <mhiramat@...nel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	linux-kernel@...r.kernel.org,
	linux-trace-kernel@...r.kernel.org
Subject: [PATCH 0/5] tracing: probes: Use heap instead of stack for temporary buffers

Hi,

Here is a series of cleanup patches which allocate temporary buffers
and objects on heap (slab) instead of the stack. This reduces a
possibility of stack overflow. This may reduce the performance but
the modified path is not a hot path.

---

Masami Hiramatsu (Google) (5):
      tracing: probe: Allocate traceprobe_parse_context from heap
      tracing: fprobe-event: Allocate string buffers from heap
      tracing: kprobe-event: Allocate string buffers from heap
      tracing: eprobe-event: Allocate string buffers from heap
      tracing: uprobe-event: Allocate string buffers from heap


 kernel/trace/trace_eprobe.c |   38 +++++++++++++++++++++++--------
 kernel/trace/trace_fprobe.c |   52 ++++++++++++++++++++++++++++---------------
 kernel/trace/trace_kprobe.c |   49 ++++++++++++++++++++++++++---------------
 kernel/trace/trace_probe.h  |    9 +++++++
 kernel/trace/trace_uprobe.c |   37 ++++++++++++++++++++++---------
 5 files changed, 129 insertions(+), 56 deletions(-)

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