From: Andreas Henriksson <andreas@fatal.se>
To: Patrick McHardy <kaber@trash.net>, Alexander Wirt <formorer@debian.org>
Cc: shemminger@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: iproute2: resend of patches from Debian.
Date: Thu, 11 Oct 2007 23:22:12 +0200 [thread overview]
Message-ID: <1192137732.4733.34.camel@localhost.localdomain> (raw)
In-Reply-To: <470E87EA.4030200@trash.net>
On tor, 2007-10-11 at 22:30 +0200, Patrick McHardy wrote:
> Andreas Henriksson wrote:
> > Abort flush after 10 seconds.
>
> This should be optional IMO.
Copying Alexander Wirt here again, as I think this is his patch.
I'll skip this patch in my next resend...
>
> > Add references to lartc, also drop bogus reference to tc-filters
>
> There's a bad habit of reporting bugs on lartc that belong to netdev,
> please also make it perfectly clear that lartc is not for bug-reports.
I'll update the patch to mention this.
>
> > Fix overflow in time2tick / tick2time.
> >
> > The helper functions gets passed an unsigned int, which gets cast to long
> > and overflows.
> >
> > See Debian bug #175462 - http://bugs.debian.org/175462
> >
> > Signed-off-by: Andreas Henriksson <andreas@fatal.se>
> >
> > diff -uri iproute-20070313.orig/tc/tc_core.c iproute-20070313/tc/tc_core.c
> > --- iproute-20070313.orig/tc/tc_core.c 2007-03-13 22:50:56.000000000 +0100
> > +++ iproute-20070313/tc/tc_core.c 2007-08-15 00:41:30.000000000 +0200
> > @@ -35,12 +35,12 @@
> > }
> >
> >
> > -long tc_core_time2tick(long time)
> > +unsigned tc_core_time2tick(unsigned time)
> > {
> > return time*tick_in_usec;
> > }
> >
> > -long tc_core_tick2time(long tick)
> > +unsigned tc_core_tick2time(unsigned tick)
> > {
> > return tick/tick_in_usec;
> > }
>
> What about the other functions returning long? I think all of these
> should be unsigned.
Since I'm no superhacker, I was afraid to touch anything else then the
things I could test and this change is what's needed to fix the reported
bug. (Actually only one of them was needed IIRC, but it would be stupid
to only change one.)
I'll have a look at the other helper functions as well, probably adding
a separate patch so that it can be easily dropped if I screw something
up there.. :)
I'll also drop the mpath stuff you mentioned in the other mail...
Thanks for reviewing the patches!
--
Regards,
Andreas Henriksson
next prev parent reply other threads:[~2007-10-11 21:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 18:25 iproute2: resend of patches from Debian Andreas Henriksson
2007-10-11 19:25 ` Lennart Sorensen
2007-10-11 19:59 ` Andreas Henriksson
2007-10-12 5:55 ` Alexander Wirt
2007-10-11 20:11 ` Stephen Hemminger
2007-10-11 20:32 ` Andreas Henriksson
2007-10-11 20:30 ` Patrick McHardy
2007-10-11 21:22 ` Andreas Henriksson [this message]
2007-10-11 21:48 ` David Miller
2007-10-11 22:35 ` Andreas Henriksson
2007-10-11 22:38 ` David Miller
2007-10-12 5:50 ` Alexander Wirt
2007-10-12 8:34 ` David Miller
2007-10-11 23:54 ` Stephen Hemminger
2007-10-11 21:05 ` Patrick McHardy
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=1192137732.4733.34.camel@localhost.localdomain \
--to=andreas@fatal.se \
--cc=formorer@debian.org \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).