Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] pkt_sched: Fix lockdep warning on est_tree_lock in gen_estimator
Date: Fri, 03 Sep 2010 07:26:45 +0200	[thread overview]
Message-ID: <1283491605.3699.1378.camel@edumazet-laptop> (raw)
In-Reply-To: <20100902205535.GB3089@del.dom.local>

Le jeudi 02 septembre 2010 à 22:55 +0200, Jarek Poplawski a écrit :
> On Thu, Sep 02, 2010 at 10:32:01PM +0200, Eric Dumazet wrote:
> > Le jeudi 02 septembre 2010 ?? 13:22 -0700, David Miller a écrit :
> > > From: Jarek Poplawski <jarkao2@gmail.com>
> > > Date: Thu, 2 Sep 2010 22:12:58 +0200
> > > 
> > > > This patch fixes a lockdep warning:
> > > > 
> > > > [  516.287584] =========================================================
> > > > [  516.288386] [ INFO: possible irq lock inversion dependency detected ]
> > > > [  516.288386] 2.6.35b #7
> > > > [  516.288386] ---------------------------------------------------------
> > > > [  516.288386] swapper/0 just changed the state of lock:
> > > > [  516.288386]  (&qdisc_tx_lock){+.-...}, at: [<c12eacda>] est_timer+0x62/0x1b4
> > > > [  516.288386] but this lock took another, SOFTIRQ-unsafe lock in the past:
> > > > [  516.288386]  (est_tree_lock){+.+...}
> > > > [  516.288386] 
> > > > [  516.288386] and interrupts could create inverse lock ordering between them.
> > > > ...
> > > > 
> > > > So, est_tree_lock needs BH protection because it's taken by
> > > > qdisc_tx_lock, which is used both in BH and process contexts.
> > > > (Full warning with this patch at netdev, 02 Sep 2010.)
> > > > 
> > > > Fixes commit: ae638c47dc040b8def16d05dc6acdd527628f231
> > > > 
> > > > Signed-off-by: Jarek Poplawski <jarkao2@gmail.com>
> > > 
> > > Applied, thanks Jarek.
> > > 
> > > Eric, please make an effort to run with lockdep enabled when making
> > > locking changes, just for fun :-)
> > 
> > Hmm... I still trying to understand the problem.
> > 
> > I dont understand Jarek analysis yet.
> > 
> 
> cpu1:					cpu2:
> (process)				(process)
> qdisc_tx_lock				est_tree_lock
> (waiting for est_tree_lock)		(bh)
> 					(waiting for qdisc_tx_lock)
> 

Cool. Reading commit ae638c47dc040b, I thought only RTNL was possibly
hold in these paths.

Thanks Jarek !




  reply	other threads:[~2010-09-03  5:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 20:12 [PATCH] pkt_sched: Fix lockdep warning on est_tree_lock in gen_estimator Jarek Poplawski
2010-09-02 20:22 ` David Miller
2010-09-02 20:32   ` Eric Dumazet
2010-09-02 20:55     ` Jarek Poplawski
2010-09-03  5:26       ` Eric Dumazet [this message]
2010-09-02 20:53 ` Eric Dumazet
2010-09-02 20:59   ` David Miller
2010-09-02 21:22   ` 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=1283491605.3699.1378.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jarkao2@gmail.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox