From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 iproute2] get_rate: detect 32bit overflows
Date: Mon, 03 Jun 2013 08:51:33 -0700 [thread overview]
Message-ID: <1370274693.24311.154.camel@edumazet-glaptop> (raw)
In-Reply-To: <1370273807.1918.20.camel@bwh-desktop.uk.level5networks.com>
On Mon, 2013-06-03 at 16:36 +0100, Ben Hutchings wrote:
> Oops, I read this as being strtol() currently, not strtod(). Currently
> '1.5gbit' will work, but this change will break that. So I think you
> need to keep bps as a double.
Arg
> Then here I think the check should be *rate != floor(bps), i.e. accept
> rounding down of a non-integer number of bytes but any other change is
> assumed to be overflow.
Thanks Ben, here is v4 then ;)
[PATCH v4] get_rate: detect 32bit overflows
Current rate limit is 34.359.738.360 bit per second, and
unfortunately 40Gbps links are above it.
overflows in get_rate() are currently not detected, and some
users are confused. Let's detect this and complain.
Note that some qdisc are ready to get extended range, but this will
need additional attributes and new iproute2
With help from Ben Hutchings
Signed-off-by: Eric Dumazet <edumazet@google.com>
---
tc/tc_util.c | 20 ++++++++++++--------
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/tc/tc_util.c b/tc/tc_util.c
index 8e62a01..8114c97 100644
--- a/tc/tc_util.c
+++ b/tc/tc_util.c
@@ -152,19 +152,23 @@ int get_rate(unsigned *rate, const char *str)
if (p == str)
return -1;
- if (*p == '\0') {
- *rate = bps / 8.; /* assume bits/sec */
- return 0;
- }
-
for (s = suffixes; s->name; ++s) {
if (strcasecmp(s->name, p) == 0) {
- *rate = (bps * s->scale) / 8.;
- return 0;
+ bps *= s->scale;
+ p += strlen(p);
+ break;
}
}
- return -1;
+ if (*p)
+ return -1; /* unknown suffix */
+
+ bps /= 8; /* -> bytes per second */
+ *rate = bps;
+ /* detect if an overflow happened */
+ if (*rate != floor(bps))
+ return -1;
+ return 0;
}
void print_rate(char *buf, int len, __u32 rate)
next prev parent reply other threads:[~2013-06-03 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 18:51 [PATCH iproute2] get_rate: detect 32bit overflows Eric Dumazet
2013-06-02 21:30 ` Eric Dumazet
2013-06-02 21:36 ` [PATCH v2 " Eric Dumazet
2013-06-03 14:37 ` Ben Hutchings
2013-06-03 15:19 ` Eric Dumazet
2013-06-03 15:36 ` Ben Hutchings
2013-06-03 15:51 ` Eric Dumazet [this message]
2013-06-03 16:31 ` Ben Hutchings
2013-06-07 16:25 ` Stephen Hemminger
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=1370274693.24311.154.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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