netdev - Re: [PATCH 1/1] net/mlx5: query_mcia_reg fail logging at debug severity

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: <742b1cd3-5935-44dd-bc3d-5744b56aa861@nvidia.com>
Date: Sun, 2 Nov 2025 15:09:28 +0200
From: Gal Pressman <gal@...dia.com>
To: Matthew W Carlis <mattc@...estorage.com>
Cc: adailey@...estorage.com, ashishk@...estorage.com, kuba@...nel.org,
 mbloch@...dia.com, msaggi@...estorage.com, netdev@...r.kernel.org,
 saeedm@...dia.com, tariqt@...dia.com
Subject: Re: [PATCH 1/1] net/mlx5: query_mcia_reg fail logging at debug
 severity

On 30/10/2025 22:09, Matthew W Carlis wrote:
> On Thu, 30 Oct 2025 16:48:54, Gal Pressman wrote:
>> I asked before, maybe these automatic tools that keep querying the
>> module continue to do so because of the success return code, and that
>> will be resolved soon?
> 
> I went and ran the command on a port with no module and agree that it does
> return zero. 
> 
> It doesn't solve the problem for me... Part of the reason automation will
> periodically run the command is for inventory purposes. We want to roughly
> know when a module was installed or removed. Then, as far as I can tell the
> only way to know if a module is installed is by running this command which
> has the consequence of generating log spam when there is not a module installed.
> 
>> Changing the log level makes things more difficult, as most production
>> servers will not enable the debug print, and the logs would be harder to
>> analyze.
> 
> I care less about the logging level... I suspect it should be info or dbg, but
> we just don't want log lines generated when we're trying to figure out if some
> module is installed.

I have an idea on how to make the situation better, will hopefully have
something soon.