From: Florian Fainelli <f.fainelli@gmail.com>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Renjith R V <renjith.rv@quest-global.com>
Subject: Re: [PATCH] net: ethtool: remove error check for legacy setting transceiver type
Date: Thu, 19 Oct 2017 16:38:02 -0700 [thread overview]
Message-ID: <d0968770-23e4-b195-c0d5-fdf15878a684@gmail.com> (raw)
In-Reply-To: <20171019233208.15444-1-niklas.soderlund+renesas@ragnatech.se>
On 10/19/2017 04:32 PM, Niklas Söderlund wrote:
> Commit 9cab88726929605 ("net: ethtool: Add back transceiver type")
> restores the transceiver type to struct ethtool_link_settings and
> convert_link_ksettings_to_legacy_settings() but forgets to remove the
> error check for the same in convert_legacy_settings_to_link_ksettings().
> This prevents older versions of ethtool to change link settings.
>
> # ethtool --version
> ethtool version 3.16
>
> # ethtool -s eth0 autoneg on speed 100 duplex full
> Cannot set new settings: Invalid argument
> not setting speed
> not setting duplex
> not setting autoneg
>
> While newer versions of ethtool works.
>
> # ethtool --version
> ethtool version 4.10
>
> # ethtool -s eth0 autoneg on speed 100 duplex full
> [ 57.703268] sh-eth ee700000.ethernet eth0: Link is Down
> [ 59.618227] sh-eth ee700000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
>
> Fixes: 19cab88726929605 ("net: ethtool: Add back transceiver type")
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
Good catch, thanks Niklas! Surprisingly I was also testing with an older
version of ethtool but I realize I was mostly testing the "get" part and
not the "set" part, so clearly an oversight here...
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> net/core/ethtool.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> Hi,
>
> The commit 9cab88726929605 ("net: ethtool: Add back transceiver type")
> itself is not enough to trigger the error, the commit after it is also
> needed ceb628134a75564d ("net: phy: Keep reporting transceiver type").
> This is because the later sets cmd->base.transceiver so that the type
> can be reported and the fault triggered. I hope however I did the
> correct thing with the Fixes tag.
Both having made it in the same release, that should be fine, thanks!
>
> diff --git a/net/core/ethtool.c b/net/core/ethtool.c
> index 3228411ada0fa77e..9a9a3d77e3274fc3 100644
> --- a/net/core/ethtool.c
> +++ b/net/core/ethtool.c
> @@ -436,7 +436,7 @@ bool ethtool_convert_link_mode_to_legacy_u32(u32 *legacy_u32,
> EXPORT_SYMBOL(ethtool_convert_link_mode_to_legacy_u32);
>
> /* return false if legacy contained non-0 deprecated fields
> - * transceiver/maxtxpkt/maxrxpkt. rest of ksettings always updated
> + * maxtxpkt/maxrxpkt. rest of ksettings always updated
> */
> static bool
> convert_legacy_settings_to_link_ksettings(
> @@ -451,8 +451,7 @@ convert_legacy_settings_to_link_ksettings(
> * deprecated legacy fields, and they should not use
> * %ETHTOOL_GLINKSETTINGS/%ETHTOOL_SLINKSETTINGS
> */
> - if (legacy_settings->transceiver ||
> - legacy_settings->maxtxpkt ||
> + if (legacy_settings->maxtxpkt ||
> legacy_settings->maxrxpkt)
> retval = false;
>
>
--
Florian
next prev parent reply other threads:[~2017-10-19 23:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 23:32 [PATCH] net: ethtool: remove error check for legacy setting transceiver type Niklas Söderlund
2017-10-19 23:38 ` Florian Fainelli [this message]
2017-10-20 7:15 ` Geert Uytterhoeven
2017-10-20 9:41 ` Niklas Söderlund
2017-10-20 13:03 ` Niklas Söderlund
2017-10-22 1:15 ` David Miller
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=d0968770-23e4-b195-c0d5-fdf15878a684@gmail.com \
--to=f.fainelli@gmail.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=renjith.rv@quest-global.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).