linux-kernel - Re: [PATCH v4 4/6] tracing: Guard __DECLARE_TRACE() use of __DO_TRACE

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: <20250723182930.2d0d59f1@gandalf.local.home>
Date: Wed, 23 Jul 2025 18:29:30 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, rcu@...r.kernel.org,
 linux-kernel@...r.kernel.org, kernel-team@...a.com, Sebastian Andrzej
 Siewior <bigeasy@...utronix.de>, bpf@...r.kernel.org
Subject: Re: [PATCH v4 4/6] tracing: Guard __DECLARE_TRACE() use of
 __DO_TRACE_CALL() with SRCU-fast

On Wed, 23 Jul 2025 15:17:52 -0700
"Paul E. McKenney" <paulmck@...nel.org> wrote:

> I believe that Steve provided me with the essentials for perf and ftrace,
> but please check:  f808f53d4e4f ("squash! tracing: Guard __DECLARE_TRACE()
> use of __DO_TRACE_CALL() with SRCU-fast").

Note, there's nothing in the ftrace side that requires preemption disabled,
but it assumes that it is, and adjusts the preempt_count that is recorded
in the trace event to accommodate it.

-- Steve