linux-kernel - Re: [PATCH 5/5] rtla/timerlat_top: Abort event processing on second signal

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: <20250116195725.2afc9f88@gandalf.local.home>
Date: Thu, 16 Jan 2025 19:57:25 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Tomas Glozar <tglozar@...hat.com>
Cc: linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org, John
 Kacur <jkacur@...hat.com>, Luis Goncalves <lgoncalv@...hat.com>, Gabriele
 Monaco <gmonaco@...hat.com>
Subject: Re: [PATCH 5/5] rtla/timerlat_top: Abort event processing on second
 signal

On Thu, 16 Jan 2025 15:49:31 +0100
Tomas Glozar <tglozar@...hat.com> wrote:

> Apply the changes from the previous patch also to timerlat-top.
> 

Same here. I replaced this with:

    rtla/timerlat_top: Abort event processing on second signal
    
    If either SIGINT is received twice, or after a SIGALRM (that is, after
    timerlat was supposed to stop), abort processing events currently left
    in the tracefs buffer and exit immediately.
    
    This allows the user to exit rtla without waiting for processing all
    events, should that take longer than wanted, at the cost of not
    processing all samples.

-- Steve