[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251119231115.8722-1-mattc@purestorage.com>
Date: Wed, 19 Nov 2025 16:11:15 -0700
From: Matthew W Carlis <mattc@...estorage.com>
To: tariqt@...dia.com
Cc: andrew+netdev@...n.ch,
davem@...emloft.net,
dtatulea@...dia.com,
edumazet@...gle.com,
gal@...dia.com,
kuba@...nel.org,
leon@...nel.org,
linux-kernel@...r.kernel.org,
linux-rdma@...r.kernel.org,
mattc@...estorage.com,
mbloch@...dia.com,
moshe@...dia.com,
netdev@...r.kernel.org,
pabeni@...hat.com,
richardcochran@...il.com,
saeedm@...dia.com
Subject: Re: [PATCH net-next 1/5] net/mlx5: Refactor EEPROM query error handling to return status separately
On Mon, 17 Nov 2025 23:42:05 +0200, Gal Pressman said
> Matthew and Jakub reported [1] issues where inventory automation tools
> are calling EEPROM query repeatedly on a port that doesn't have an SFP
> connected, resulting in millions of error prints.
I'm not very familiar with the networking stack in general, but I poked around a
little trying to be able to come up with a meaningful review. I noticed that in
ethtool there are two methods registered for "ethtool -m".. Looks like it first
prefers a netlink method, but also may fall back on an ioctl implementation.
Will users who end up in the ioctl path expect to see the kernel message? In the
case of users who run "ethtool -m" on a device without a transceiver installed I
think we should expect to see something as follows? (Is this correct?)
$ ethtool -m ethx
"netlink error: mlx5: Query module eeprom by page failed, read xxx bytes, err xxx, status xxx"
Thank you for helping on this issue.
-Matt
Powered by blists - more mailing lists