From: Jarek Poplawski <jarkao2@o2.pl>
To: Patrick McHardy <kaber@trash.net>
Cc: Ranko Zivojnovic <ranko@spidernet.net>,
akpm@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: + gen_estimator-fix-locking-and-timer-related-bugs.patch added to -mm tree
Date: Mon, 9 Jul 2007 09:47:23 +0200 [thread overview]
Message-ID: <20070709074722.GA1851@ff.dom.local> (raw)
In-Reply-To: <Pine.LNX.4.64.0707071704370.1808@x2>
On Sat, Jul 07, 2007 at 05:10:54PM +0200, Patrick McHardy wrote:
> On Sat, 7 Jul 2007, Ranko Zivojnovic wrote:
>
> >>On Fri, 2007-07-06 at 16:21 +0200, Patrick McHardy wrote:
> >>>There is at least one ABBA deadlock, est_timer does:
> >>>
> >>>read_lock(&est_lock)
> >>>spin_lock(e->stats_lock) (which is dev->queue_lock)
> >>>
> >>>and qdisc_destroy calls htb_destroy under dev->queue_lock, which
> >>>calls htb_destroy_class, then gen_kill_estimator and this
> >>>write_locks est_lock.
> >>>
> >>>I can't see the problem above though, the qdisc_run path only takes
> >>>dev->queue_lock. Please enable lockdep and post the output if any.
> >>
> >
> >I've got both code paths this time. It shows exactly the ABBA deadlock
> >you describe above. The details are below.
>
>
> Thanks. I'm still wondering whats causing the other lockup
> you're seeing.
>
> >Maybe the appropriate way to fix this would to call gen_kill_estimator,
> >with the appropriate lock order, before the call to qdisc_destroy, so
> >when dev->queue_lock is taken for qdisc_destroy - the structure is
> >already off the list.
>
>
> Probably easier to just kill est_lock and use rcu lists.
> I'm currently travelling, I'll look into it tomorrow.
>
Congratulations to both of you!
Ranko, it looks like you have some licence to kill!
(I hope bugs only...)
Cheers,
Jarek P.
next prev parent reply other threads:[~2007-07-09 7:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200706271921.l5RJLgCC003910@imap1.linux-foundation.org>
[not found] ` <1183642800.3789.11.camel@ranko-fc2.spidernet.net>
[not found] ` <20070705142135.GG4759@ff.dom.local>
[not found] ` <1183646029.4069.11.camel@ranko-fc2.spidernet.net>
[not found] ` <1183651165.4069.26.camel@ranko-fc2.spidernet.net>
2007-07-06 6:14 ` + gen_estimator-fix-locking-and-timer-related-bugs.patch added to -mm tree Jarek Poplawski
2007-07-06 6:20 ` Fwd: " Jarek Poplawski
2007-07-06 6:26 ` Jarek Poplawski
2007-07-06 6:45 ` Jarek Poplawski
2007-07-06 12:47 ` Jarek Poplawski
2007-07-06 13:16 ` Ranko Zivojnovic
2007-07-09 8:25 ` Jarek Poplawski
2007-07-06 13:14 ` Ranko Zivojnovic
2007-07-06 13:27 ` Patrick McHardy
2007-07-06 13:59 ` Ranko Zivojnovic
2007-07-06 14:21 ` Patrick McHardy
2007-07-06 14:55 ` Ranko Zivojnovic
2007-07-07 7:55 ` Ranko Zivojnovic
2007-07-07 15:10 ` Patrick McHardy
2007-07-09 7:47 ` Jarek Poplawski [this message]
2007-07-09 12:41 ` Ranko Zivojnovic
2007-07-09 13:52 ` Patrick McHardy
2007-07-09 16:43 ` Ranko Zivojnovic
2007-07-09 16:54 ` Patrick McHardy
2007-07-10 7:34 ` Jarek Poplawski
2007-07-10 10:09 ` Ranko Zivojnovic
2007-07-10 12:17 ` Jarek Poplawski
2007-07-10 12:20 ` Patrick McHardy
2007-07-10 13:10 ` Jarek Poplawski
2007-07-10 13:51 ` Jarek Poplawski
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=20070709074722.GA1851@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=akpm@linux-foundation.org \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=ranko@spidernet.net \
/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).