From: bert hubert <ahu@ds9a.nl>
To: kuznet@ms2.inr.ac.ru
Cc: Alberto Bertogli <albertogli@telpin.COM.AR>, netdev@oss.sgi.com
Subject: Re: Frozen machine with adding a tc filter
Date: Mon, 22 Jul 2002 23:21:11 +0200 [thread overview]
Message-ID: <20020722212111.GA22916@outpost.ds9a.nl> (raw)
In-Reply-To: <200207222046.AAA14255@sex.inr.ac.ru>
On Tue, Jul 23, 2002 at 12:46:44AM +0400, kuznet@ms2.inr.ac.ru wrote:
> Hello!
>
> > I know it's weird, but anyway i don't think that a lockup is the error the
> > user deserves =)
>
> You really deserved this.
I also reported this - should tc check this? Or the kernel? I think each
qdisc implements its own filter hooks and rules, so tc may be a nice place
to do at least simple checking, although it cannot easily spot complicated
loops.
if ((cl = (void*)res.class) == NULL) {
if (TC_H_MAJ(res.classid))
cl = cbq_class_lookup(q, res.classid);
else if ((cl = defmap[res.classid&TC_PRIO_MAX]) == NULL
cl = defmap[TC_PRIO_BESTEFFORT];
if (cl == NULL || cl->level >= head->level)
goto fallback;
}
Aren't the last 2 lines meant to prevent this from happening?
(net/sched/sch_cbq.c).
Please tell me your ideas, I hope to fix this. I know people who've had this
happen by accident and they really hate it.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2002-07-22 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 3:49 Frozen machine with adding a tc filter Alberto Bertogli
2002-07-22 20:46 ` kuznet
2002-07-22 21:21 ` bert hubert [this message]
2002-07-22 22:57 ` kuznet
2002-07-23 21:28 ` bert hubert
2002-07-23 21:56 ` kuznet
2002-07-23 22:11 ` bert hubert
2002-07-23 22:19 ` kuznet
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=20020722212111.GA22916@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=albertogli@telpin.COM.AR \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
/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).