linux-kernel - Re: [PATCH v3 10/13] rv: Add support for per-object monitors in DA/HA

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: <87o6nwi726.fsf@yellow.woof>
Date: Thu, 18 Dec 2025 14:26:57 +0700
From: Nam Cao <namcao@...utronix.de>
To: Gabriele Monaco <gmonaco@...hat.com>, linux-kernel@...r.kernel.org,
 Steven Rostedt <rostedt@...dmis.org>, Gabriele Monaco
 <gmonaco@...hat.com>, linux-trace-kernel@...r.kernel.org
Cc: Tomas Glozar <tglozar@...hat.com>, Juri Lelli <jlelli@...hat.com>, Clark
 Williams <williams@...hat.com>, John Kacur <jkacur@...hat.com>
Subject: Re: [PATCH v3 10/13] rv: Add support for per-object monitors in DA/HA

Gabriele Monaco <gmonaco@...hat.com> writes:
> RV deterministic and hybrid automata currently only support global,
> per-cpu and per-task monitors. It isn't possible to write a model that
> would follow some different type of object, like a deadline entity or a
> lock.
>
> Define the generic per-object monitor implementation which shares part
> of the implementation with the per-task monitors.
> The user needs to provide an id for the object (e.g. pid for tasks) and
> define the data type for the monitor_target (e.g. struct task_struct *
> for tasks). Both are supplied to the event handlers, as the id may not
> be easily available in the target.
>
> The monitor storage (e.g. the rv monitor, pointer to the target, etc.)
> is stored in a hash table indexed by id. Monitor storage objects are
> automatically allocated unless specified otherwise (e.g. if the creation
> context is unsafe for allocation).
>
> Signed-off-by: Gabriele Monaco <gmonaco@...hat.com>

Reviewed-by: Nam Cao <namcao@...utronix.de>