linux-kernel - Re: [PATCH] rv: Add signal reactor

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87ikgxqrna.fsf@yellow.woof>
Date: Thu, 02 Oct 2025 16:56:09 +0200
From: Nam Cao <namcao@...utronix.de>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>,
 Gabriele Monaco
 <gmonaco@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, Steven
 Rostedt <rostedt@...dmis.org>, Masami Hiramatsu <mhiramat@...nel.org>,
 Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: [PATCH] rv: Add signal reactor

Thomas Weißschuh <thomas.weissschuh@...utronix.de> writes:
> I am wondering if it would make sense to add a new tracepoint that
> fires in addition of the reactors. That would allow multiple
> simultaneous consumers and also bespoke handlers in userspace.

We do have tracepoints for each monitor in: kernel/trace/rv/rv_trace.h

And yeah, I think it is a nice idea for all the consumers to use these
tracepoints intead (that includes rtapp testing, and also the existing
reactors). It would simplify things, as the monitors do not have to
worry about the reactors, they only need to invoke tracepoints.

But this also makes me think about the necessity of the existing
reactors. What do they offer that tracepoints do not? Myself I almost
never use the reactors, so I'm thinking about removing them. But maybe
@Gabriele has objections?

Nam