linux-kernel - Re: [PATCH v2 1/2] tracing: Make the backup instance readonly

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-prev] [day] [month] [year] [list]

Message-Id: <20260113150458.8633891cf9f377565642124b@kernel.org>
Date: Tue, 13 Jan 2026 15:04:58 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
 linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] tracing: Make the backup instance readonly

On Mon, 12 Jan 2026 19:47:22 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Mon, 12 Jan 2026 19:45:51 -0500
> Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > Let's not add any flags to the eventfs_entry. That is created for every
> > event, and events are already too big in size. I don't want to increase the
> > size of each event for this feature.
> 
> Actually, there's not many of these. But they are all static variables. How
> are you going to differentiate them?

Since the format/id files are always readonly, so we can put a mode flag on
each entry.

Anyway, I will just share the readonly entries in the same array, but
put them at the beginning of it.

Let me update it to v3.

Thanks, 

> 
> -- Steve
> 


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