netdev - [PATCH 0/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-next>] [day] [month] [year] [list]

Message-ID: <20251028194011.39877-1-mattc@purestorage.com>
Date: Tue, 28 Oct 2025 13:40:10 -0600
From: Matthew W Carlis <mattc@...estorage.com>
To: netdev@...r.kernel.org
Cc: saeedm@...dia.com,
	tariqt@...dia.com,
	mbloch@...dia.com,
	ashishk@...estorage.com,
	msaggi@...estorage.com,
	adailey@...estorage.com,
	Matthew W Carlis <mattc@...estorage.com>
Subject: [PATCH 0/1] net/mlx5: query_mcia_reg fail logging at debug severity

The commit message pretty much has most of my thoughts on this one. We
see this message generated all the time because users are trying to
determine if there is an SFP module installed in a port or when trying
to get module info from a port that doesn't have an SFP module. This
is not really an error at all & therefore the message is undesirable.
Downgrading the log severity for this message to dbg allows users to
control it via dyndbg & therefore "up to the user to decide" if they
care about it.

Matthew W Carlis (1):
  net/mlx5: query_mcia_reg fail logging at debug severity

 drivers/net/ethernet/mellanox/mlx5/core/port.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
2.46.0