linux-kernel - Re: [PATCH] tracing: fix race when creating trace probe log error message

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: <20250501165836.3b943e44@gandalf.local.home>
Date: Thu, 1 May 2025 16:58:36 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Paul Cacheux <paulcacheux@...il.com>
Cc: Paul Cacheux via B4 Relay  <devnull+paulcacheux.gmail.com@...nel.org>,
 Masami Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers 
 <mathieu.desnoyers@...icios.com>, linux-kernel@...r.kernel.org,
 linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH] tracing: fix race when creating trace probe log error
 message

On Thu, 01 May 2025 22:56:44 +0200
Paul Cacheux <paulcacheux@...il.com> wrote:

> Just to double check, what you are suggesting here is to include a
> mutex in the shared trace_probe_log entry, and to lock it in all
> accessors functions (trace_probe_log_{init,set_index,clear,err})?

Yep!

-- Steve