linux-kernel - Re: [PATCH v1] rtla: Set distinctive exit value for failed tests

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: <CADDUTFzrUz9811qtOyvTObJnB61UoejxdXAqxV5Qr8bB9fD4ZA@mail.gmail.com>
Date: Thu, 17 Apr 2025 11:47:36 +0300
From: Costa Shulyupin <costa.shul@...hat.com>
To: Tomas Glozar <tglozar@...hat.com>
Cc: Steven Rostedt <rostedt@...dmis.org>, John Kacur <jkacur@...hat.com>, 
	"Luis Claudio R. Goncalves" <lgoncalv@...hat.com>, Eder Zulian <ezulian@...hat.com>, 
	Dan Carpenter <dan.carpenter@...aro.org>, Jan Stancek <jstancek@...hat.com>, 
	linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] rtla: Set distinctive exit value for failed tests

On Mon, 31 Mar 2025 at 09:30, Tomas Glozar <tglozar@...hat.com> wrote:
> Also, users might be already relying on rtla exiting with 0 on
> threshold violation. What do you think about adding a new command line
> argument, `--fail-on-threshold`, that would allow the user (including
> the test suite) to trigger the new behavior?
Although it is technically possible to rely on a failed value zero, I
suppose it is very unexpected. I expect current users only grep the
output of rtla.
I think adding a new command line argument is overcomplicated. Adding
a new command-line argument for this seems unnecessarily complex, and
I'm not aware of any Linux/POSIX tools that offer such an option.

Costa