linux-kernel - [PATCH 0/2] tracing: Remove backup instance after read all

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:  <176779714767.4193242.1978666866487010024.stgit@mhiramat.tok.corp.google.com>
Date: Wed,  7 Jan 2026 23:45:48 +0900
From: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Masami Hiramatsu <mhiramat@...nel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	linux-kernel@...r.kernel.org,
	linux-trace-kernel@...r.kernel.org
Subject: [PATCH 0/2] tracing: Remove backup instance after read all

Hi,

This series of patches improves backup instances of the persistent
ring buffer. Since backup instances are a kind of snapshot of the
persistent ring buffer, it should be readonly. And if it is readonly
there is no reason to keep it after reading all data via trace_pipe
because the data has been consumed.
Thus, [1/2] makes backup instances readonly (not able to write any
events, cleanup trace, change buffer size). Also, [2/2] removes the
backup instance after consuming all data via trace_pipe.
With this improvements, even if we makes a backup instance (using
the same amount of memory of the persistent ring buffer), it will
be removed after reading the data automatically.

---

Masami Hiramatsu (Google) (2):
      tracing: Make the backup instance readonly
      tracing: Add autoremove feature to the backup instance

 kernel/trace/trace.c        |  155 ++++++++++++++++++++++++++++++++++++-------
 kernel/trace/trace.h        |   12 +++
 kernel/trace/trace_events.c |   14 +++-
 3 files changed, 153 insertions(+), 28 deletions(-)

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