linux-kernel - Re: [PATCH] rtla: clarify trace option syntax in documentation and usage help

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: <20250724095627.572c1cff@batman.local.home>
Date: Thu, 24 Jul 2025 09:56:27 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Ivan Pravdin <ipravdin.official@...il.com>
Cc: bristot@...nel.org, corbet@....net, linux-trace-kernel@...r.kernel.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rtla: clarify trace option syntax in documentation and
 usage help

On Tue, 22 Jul 2025 21:52:33 -0400
Ivan Pravdin <ipravdin.official@...il.com> wrote:

> When using `rtla timerlat {top,hist}`, the `-t/--trace` option is
> optional. However, when providing a filename, the long option requires
> an equal sign (`=`), i.e., `--trace=<file>`. This is because the
> command-line parser treats `--trace` without `=` as a flag with no
> value, leading to unexpected behavior.
> 
> Valid usage:
>     - `-t[file]`
>     - `-t=[file]`
>     - `--trace=[file]`
> 
> Invalid usage:
>     - `-t [file]`
>     - `--trace [file]`

I wonder if the better fix would be to make the above valid?

-- Steve


> 
> Clarify valid usage in documentation and help message.
> 
> Signed-off-by: Ivan Pravdin <ipravdin.official@...il.com>