mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: davem@davemloft.net, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net-sysfs: Report link speed only when possible
Date: Fri, 6 Jun 2014 10:57:33 +0200	[thread overview]
Message-ID: <20140606085733.GJ2984@minipsycho.orion> (raw)
In-Reply-To: <771f792d4d4391c656305a522557c53c4e84a666.1402043894.git.mprivozn@redhat.com>

Fri, Jun 06, 2014 at 10:40:30AM CEST, mprivozn@redhat.com wrote:
>The link speed is available at /sys/class/net/$nic/speed.
>However, in some cases, depending on the driver, if the link is
>not plugged, -1 is reported (this is the case of e1000e for
>instance). To make things worse, the value is printed out as an

Actually, SPEED_UNKNOWN is also -1
So e1000e is not any exception.


>unsigned integer, so you'll get this shady number which you can't
>evaluate correctly. This is actually a regression in 3.X kernels
>as the commit that broke things is 8ae6daca. With this change,
>you'll get -EINVAL whenever a -1 is to be printed out.
>
>Before the change:
>  # cat /sys/class/net/eth0/speed
>  4294967295
>
>After the change:
>  # cat /sys/class/net/eth0/speed
>  cat: /sys/class/net/eth0/speed: Invalid argument
>
>Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
>---
> net/core/net-sysfs.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
>diff --git a/net/core/net-sysfs.c b/net/core/net-sysfs.c
>index 1cac29e..ce4b298 100644
>--- a/net/core/net-sysfs.c
>+++ b/net/core/net-sysfs.c
>@@ -172,8 +172,13 @@ static ssize_t speed_show(struct device *dev,
> 
> 	if (netif_running(netdev)) {
> 		struct ethtool_cmd cmd;
>-		if (!__ethtool_get_settings(netdev, &cmd))
>-			ret = sprintf(buf, fmt_udec, ethtool_cmd_speed(&cmd));
>+		if (!__ethtool_get_settings(netdev, &cmd)) {
>+			__u32 speed = ethtool_cmd_speed(&cmd);
>+
>+			if (speed != (__u32) -1)

Just rather use SPEED_UNKNOWN instead of -1 here.


>+				ret = sprintf(buf, fmt_udec,
>+					      ethtool_cmd_speed(&cmd));
>+		}
> 	}
> 	rtnl_unlock();
> 	return ret;
>-- 
>2.0.0
>

  reply	other threads:[~2014-06-06  8:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  8:40 Michal Privoznik
2014-06-06  8:57 ` Jiri Pirko [this message]
2014-06-06 19:54   ` David Miller
2014-06-13  9:19     ` Michal Privoznik
2014-06-13 20:03       ` David Miller
2014-06-16  7:32         ` Michal Privoznik
2014-06-16  8:11           ` David Miller
2014-06-16  8:30             ` Michal Privoznik
2014-06-16  8:44               ` David Miller
2014-06-16  8:59                 ` Michal Privoznik
2014-06-16  9:01                 ` Jiri Pirko

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=20140606085733.GJ2984@minipsycho.orion \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mprivozn@redhat.com \
    --cc=netdev@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®