From: Ido Schimmel <idosch@nvidia.com>
To: "Krzysztof Olędzki" <ole@ans.pl>
Cc: Andrew Lunn <andrew@lunn.ch>, Michal Kubecek <mkubecek@suse.cz>,
Moshe Shemesh <moshe@nvidia.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
tariqt@nvidia.com, Dan Merillat <git@dan.merillat.org>
Subject: Re: [PATCH v2 ethtool] qsfp: Better handling of Page 03h netlink read failure
Date: Wed, 31 Jul 2024 11:20:37 +0300 [thread overview]
Message-ID: <Zqnz1bn2rx5Jtw09@shredder.mtl.com> (raw)
In-Reply-To: <0d2504d1-e150-40bf-8e30-bf6414d42b60@ans.pl>
On Tue, Jul 30, 2024 at 05:49:33PM -0700, Krzysztof Olędzki wrote:
> When dumping the EEPROM contents of a QSFP transceiver module, ethtool
> will only ask the kernel to retrieve Upper Page 03h if the module
> advertised it as supported.
>
> However, some kernel drivers like mlx4 are currently unable to provide
> the page, resulting in the kernel returning an error. Since Upper Page
> 03h is optional, do not treat the error as fatal. Instead, print an
> error message and allow ethtool to continue and parse / print the
> contents of the other pages.
>
> Also, clarify potentially cryptic "netlink error: Invalid argument" message.
>
> Before:
> # ethtool -m eth3
> netlink error: Invalid argument
>
> After:
> # ethtool -m eth3
> netlink error: Invalid argument
> Failed to read Upper Page 03h, driver error?
> Identifier : 0x0d (QSFP+)
> Extended identifier : 0x00
> (...)
>
> Fixes: 25b64c66f58d ("ethtool: Add netlink handler for getmodule (-m)")
>
Nit: No blank line between Fixes and SoB, but maybe Michal can fix it up
when applying
> Signed-off-by: Krzysztof Piotr Oledzki <ole@ans.pl>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
Thanks!
next prev parent reply other threads:[~2024-07-31 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 0:49 [PATCH v2 ethtool] qsfp: Better handling of Page 03h netlink read failure Krzysztof Olędzki
2024-07-31 8:20 ` Ido Schimmel [this message]
2024-07-31 13:58 ` Krzysztof Olędzki
2024-08-01 0:16 ` Jakub Kicinski
2024-08-08 13:41 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zqnz1bn2rx5Jtw09@shredder.mtl.com \
--to=idosch@nvidia.com \
--cc=andrew@lunn.ch \
--cc=git@dan.merillat.org \
--cc=mkubecek@suse.cz \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=ole@ans.pl \
--cc=tariqt@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).