From: jamal <hadi@cyberus.ca>
To: Patrick McHardy <kaber@trash.net>
Cc: Denys <denys@visp.net.lb>,
Stephen Hemminger <shemminger@linux-foundation.org>,
netdev@vger.kernel.org
Subject: Re: one more... iproute commands lockup whole system
Date: Wed, 04 Apr 2007 09:58:22 -0400 [thread overview]
Message-ID: <1175695102.4063.4.camel@localhost> (raw)
In-Reply-To: <4613A9F6.8000307@trash.net>
On Wed, 2007-04-04 at 15:36 +0200, Patrick McHardy wrote:
>
> We have a loop counter (RTTL) in tc_verd. For some reason it is reset
> after ing_filter though.
>
Essentially it is valuable just to avoid a lot of stacking (separate
issue) and not to avoid the locking issue he is seeing.
> It would be interesting to find out what the problem is exactly.
> The configuration itself looks harmless, so I'm guessing its
> rather a deadlock than a loop.
We know it is a deadlock.
If you redirect the first time queue lock for eth0 will be held, before
it is released if you do another redirect, it will again be heading
towards eth0 and it will deadlock on grabbing the queue lock.
cheers,
jamal
next prev parent reply other threads:[~2007-04-04 13:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 18:00 iproute2-2.6.20-070313 bug ? Denys
2007-03-22 11:23 ` Patrick McHardy
2007-03-22 12:46 ` Denys
2007-03-22 13:09 ` Patrick McHardy
[not found] ` <20070322131245.M85528@visp.net.lb>
2007-03-22 13:23 ` Patrick McHardy
2007-03-22 13:35 ` Denys
[not found] ` <20070322132637.M88445@visp.net.lb>
2007-03-22 13:43 ` Patrick McHardy
2007-03-22 13:47 ` Denys
2007-03-22 13:26 ` Denys
2007-03-22 17:12 ` Stephen Hemminger
2007-03-22 17:14 ` Patrick McHardy
2007-03-26 18:49 ` more... iproute2/htb/whatever critical " Denys
2007-03-27 15:10 ` Patrick McHardy
2007-03-27 15:18 ` Denys
2007-03-27 16:00 ` Denys
2007-03-27 16:21 ` Patrick McHardy
2007-03-28 17:38 ` another " Denys
2007-03-28 23:55 ` Denys
2007-03-29 10:58 ` Patrick McHardy
2007-03-31 2:26 ` more iproute2 issues (not critical) Denys
2007-03-31 2:31 ` Denys
2007-03-31 14:16 ` Patrick McHardy
2007-04-04 0:03 ` one more... iproute commands lockup whole system Denys
2007-04-04 1:10 ` jamal
2007-04-04 1:39 ` Patrick McHardy
2007-04-04 2:09 ` jamal
2007-04-04 2:11 ` Denys
2007-04-04 10:55 ` jamal
2007-04-04 12:56 ` Denys
2007-04-04 14:10 ` jamal
2007-04-04 14:35 ` Denys
2007-04-04 14:13 ` HTB/act_mirred problem [was: one more... iproute commands lockup whole system] Patrick McHardy
2007-04-04 14:33 ` jamal
2007-04-04 14:50 ` Patrick McHardy
2007-04-05 1:33 ` jamal
2007-04-04 13:36 ` one more... iproute commands lockup whole system Patrick McHardy
2007-04-04 13:58 ` jamal [this message]
2007-04-04 14:07 ` Patrick McHardy
2007-04-04 14:30 ` jamal
2007-04-04 14:39 ` Patrick McHardy
2007-04-05 2:14 ` jamal
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=1175695102.4063.4.camel@localhost \
--to=hadi@cyberus.ca \
--cc=denys@visp.net.lb \
--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 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.