[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251030200942.38659-1-mattc@purestorage.com>
Date: Thu, 30 Oct 2025 14:09:42 -0600
From: Matthew W Carlis <mattc@...estorage.com>
To: gal@...dia.com
Cc: adailey@...estorage.com,
ashishk@...estorage.com,
kuba@...nel.org,
mattc@...estorage.com,
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 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.
Cheers!
-Matt
Powered by blists - more mailing lists