From: Ben Hutchings <bhutchings@solarflare.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 iproute2] get_rate: detect 32bit overflows
Date: Mon, 3 Jun 2013 15:37:11 +0100 [thread overview]
Message-ID: <1370270231.1918.10.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <1370209008.24311.91.camel@edumazet-glaptop>
On Sun, 2013-06-02 at 14:36 -0700, Eric Dumazet wrote:
> 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
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> ---
> v2: divide by 8 only at the right time
>
> tc/tc_util.c | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/tc/tc_util.c b/tc/tc_util.c
> index 8e62a01..8ca9d4e 100644
> --- a/tc/tc_util.c
> +++ b/tc/tc_util.c
> @@ -146,21 +146,26 @@ static const struct rate_suffix {
> int get_rate(unsigned *rate, const char *str)
> {
> char *p;
> - double bps = strtod(str, &p);
> + long long bps = strtoll(str, &p, 0);
> const struct rate_suffix *s;
>
> if (p == str)
> return -1;
>
> if (*p == '\0') {
> - *rate = bps / 8.; /* assume bits/sec */
> +common:
> + bps /= 8; /* -> bytes per second */
> + *rate = bps;
> + /* detect if an overflow happened */
> + if (*rate != bps)
> + return -1;
> return 0;
> }
>
> for (s = suffixes; s->name; ++s) {
> if (strcasecmp(s->name, p) == 0) {
> - *rate = (bps * s->scale) / 8.;
> - return 0;
> + bps *= s->scale;
> + goto common;
> }
> }
This would be more understandable without a goto. I think this ordering
would work:
for (s = suffixes; ...) {
if (...) {
bps *= s->scale;
p += strlen(s->name);
break;
}
}
if (*p)
return -1; /* unrecognised suffix */
bps /= 8;
...
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2013-06-03 14:37 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 [this message]
2013-06-03 15:19 ` Eric Dumazet
2013-06-03 15:36 ` Ben Hutchings
2013-06-03 15:51 ` Eric Dumazet
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=1370270231.1918.10.camel@bwh-desktop.uk.level5networks.com \
--to=bhutchings@solarflare.com \
--cc=eric.dumazet@gmail.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;
as well as URLs for NNTP newsgroup(s).