From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Jesper Dangaard Brouer <hawk@diku.dk>,
marek cervenka <cer20um@axpsu.fpf.slu.cz>,
linux-net@vger.kernel.org,
James Morris <jmorris@intercode.com.au>
Subject: Re: [NET_SCHED] BUG in qdisc TBF (token bucket filter)
Date: Fri, 5 Mar 2004 01:47:26 -0500 [thread overview]
Message-ID: <200403050144.17622.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0403031323140.6655@ask.diku.dk>
On Wednesday 03 March 2004 07:31 am, Jesper Dangaard Brouer wrote:
>
> BUG in qdisc TBF (token bucket filter).
>
> Problem in : Kernel 2.4.22 (and newer, tested till 2.4.25-rc2)
> Problem NOT in: kernel 2.4.21 (and older)
>
> Problem:
> --------
> After I add an tbf qdisc to an htb class, then the htb class disappear
> from the output-listing "tc -s class ls dev ethX".
>
Yeah, I botched class reporting in TBF, I am sending 2 patches as followups
to this message:
01-tbf-class-reporting.patch - actual fix
02-tbf-trailing-whitespace.patch - removes trailing whitespace from TBF code
The patches are against 2.6 but I am pretty sure they will apply to 2.4.
--
Dmitry
next prev parent reply other threads:[~2004-03-05 6:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 12:31 [NET_SCHED] BUG in qdisc TBF (token bucket filter) Jesper Dangaard Brouer
2004-03-05 6:47 ` Dmitry Torokhov [this message]
2004-03-05 6:47 ` [PATCH 1/2] NET: fix class reporting in TBF qdisc Dmitry Torokhov
2004-03-05 6:48 ` Dmitry Torokhov
2004-03-05 20:57 ` Mike Fedyk
2004-03-06 4:33 ` Dmitry Torokhov
2004-03-05 15:40 ` Problems with WLAN orinoco_pci Matthias Jim Knopf
2004-03-05 23:00 ` Peter Williams
2004-04-06 14:17 ` [NET_SCHED] BUG in qdisc TBF (token bucket filter) Jesper Dangaard Brouer
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=200403050144.17622.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=cer20um@axpsu.fpf.slu.cz \
--cc=hawk@diku.dk \
--cc=jmorris@intercode.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.