linux-kernel - Re: [PATCH] tracing: Do not allow mmap() of persistent ring buffer

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

Message-ID: <20250213212147.6511b235@gandalf.local.home>
Date: Thu, 13 Feb 2025 21:21:47 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Linux Trace Kernel
 <linux-trace-kernel@...r.kernel.org>, Mathieu Desnoyers
 <mathieu.desnoyers@...icios.com>, Vincent Donnefort <vdonnefort@...gle.com>
Subject: Re: [PATCH] tracing: Do not allow mmap() of persistent ring buffer

On Fri, 14 Feb 2025 11:07:22 +0900
Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:

> This may be good for fixing crash short term but may not allow us to read the
> subbufs which is read right before crash. Can we also add an option to reset
> the read pointer in the previous boot for the persistent ring buffer?

I'm not sure what you mean here.

Note, this is just for mmapping the buffers. Currently we never tried it as
if we did, it would have crashed. But this does not affect normal reads.

-- Steve