From: Kabelweb <office@kabelweb.at>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems with HTB shaping
Date: Thu, 11 Dec 2003 18:49:23 +0000 [thread overview]
Message-ID: <marc-lartc-107116908320924@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107096971302455@msgid-missing>
On Wednesday 10 December 2003 10:57, Ben Efros wrote:
> The answer is in your own email
>
> > > Patch against
> > > 2.4.23 and 2.6.0-test10 is here
Thank you but I was asking for a good reason: The only significant change in
the patch itself is commented as follows:
+ /* This line used to be after htb_destroy_class call below
+ and surprisingly it worked in 2.4. But it must precede it
+ because filter need its target class alive to be able to call
+ unbind_filter on it (without Oops). */
+ htb_destroy_filters(&q->filter_list);
Therefore I wanted to know whether the Ooopses fixed by the patch are known to
be possible with 2.4 as well or not. I am currently trying to find the cause
for very rare hangups (about once in two months) on a production server which
heavily uses htb.
Anyone with first-hand experience?
Best regards,
Andreas
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-12-11 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 11:24 [LARTC] Problems with HTB shaping Mindaugas Riauba
2003-12-09 20:11 ` Stef Coene
2003-12-10 5:49 ` Mindaugas Riauba
2003-12-11 6:52 ` Mindaugas Riauba
2003-12-11 9:44 ` devik
2003-12-11 11:51 ` Mindaugas Riauba
2003-12-11 14:04 ` devik
2003-12-11 14:10 ` Mindaugas Riauba
2003-12-11 14:19 ` devik
2003-12-11 18:49 ` Kabelweb [this message]
2003-12-12 14:06 ` Mindaugas Riauba
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=marc-lartc-107116908320924@msgid-missing \
--to=office@kabelweb.at \
--cc=lartc@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.