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: <a0e34d41214dd6d98e3c7b7ec37be7ad0e1812e0.camel@redhat.com>
Date: Fri, 31 Oct 2025 09:49:08 -0400
From: Crystal Wood <crwood@...hat.com>
To: Tomas Glozar <tglozar@...hat.com>, Steven Rostedt <rostedt@...dmis.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Linux Trace Kernel	
 <linux-trace-kernel@...r.kernel.org>, John Kacur <jkacur@...hat.com>, Luis
 Goncalves <lgoncalv@...hat.com>, Costa Shulyupin <costa.shul@...hat.com>,
 Wander Lairson Costa	 <wander@...hat.com>, Arnaldo Carvalho de Melo
 <acme@...nel.org>
Subject: Re: [PATCH v3 0/7] rtla/timerlat: Add --bpf-action option

On Mon, 2025-10-27 at 16:33 +0100, Tomas Glozar wrote:
> This patchset extends rtla-timerlat's BPF support with the option of
> executing a user-supplied BPF program on latency threshold overflow.
> 
> See the supplied example and documentation for how to create a program.
> bpf_tail_call() is used to chain the program with the built-in BPF
> sample collection program, if the threshold is hit.
> 
> The feature can be used for both in-kernel data collection and sending
> signals to userspace directly from the kernel, if the kernel version
> allows it.
> 
> Note: The patchset will have to be rebased on top of [1], or vice versa,
> since they both touch stop_tracing() ([1] adds one call of it, and this
> patchset adds an extra argument to it).

Probably best to add an updated version of that patch to this patchset.


> v3 changes:
> - Add tests/bpf/bpf_action_map.c to test commit (forgot to run
> git add before).

Might be nice to build that as part of "all", for the sake of people
running the tests directly (FWIW, I still don't see anything in the
makefile or engine.sh documenting how to satisfy that dependency).

In any case:
Reviewed-by: Crystal Wood <crwood@...hat.com>


-Crystal


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ