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

Message-ID: <20250218102151.56cf169b@gandalf.local.home>
Date: Tue, 18 Feb 2025 10:21:51 -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 Wed, 19 Feb 2025 00:14:24 +0900
Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:

> > As that's what added the BOOT flag and is in the same kernel version
> > that added the persistent ring buffer.  
> 
> OK, so this fix is for the limitation of the buffer which has
> TRACE_ARRAY_FL_BOOT. When this flag is introduced, it should also
> prohibit the mmap.

Correct.

-- Steve