From: Johannes Berg <johannes@sipsolutions.net>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"John W. Linville" <linville@tuxdriver.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: 2.6.37-git5 -- INFO: possible irq lock inversion dependency detected
Date: Wed, 12 Jan 2011 10:26:53 +0100 [thread overview]
Message-ID: <1294824413.3639.17.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTin4n+OQMSTdbsMBrKxhe494Uq2Db-0Fg65ao2iL@mail.gmail.com>
On Tue, 2011-01-11 at 15:10 -0500, Miles Lane wrote:
> [ INFO: possible irq lock inversion dependency detected ]
> 2.6.37-git5 #1
> ---------------------------------------------------------
> dbus-daemon/1512 just changed the state of lock:
> (&(&list->lock)->rlock#7){+.-...}, at: [<ffffffffa01d4ecc>]
> ieee80211_rx_handlers+0x36/0x1ae3 [mac80211]
> but this lock was taken by another, HARDIRQ-safe lock in the past:
> (&(&priv->lock)->rlock){-.-...}
>
> and interrupts could create inverse lock ordering between them.
Thanks Miles. I'm not sure I fully understand this trace, but I think
you can probably easily reproduce it. Would you be willing to test with
the patch on this email? I think it's related:
http://thread.gmane.org/gmane.linux.kernel.wireless.general/62842/focus=62848
johannes
prev parent reply other threads:[~2011-01-12 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 20:10 2.6.37-git5 -- INFO: possible irq lock inversion dependency detected Miles Lane
2011-01-12 9:26 ` Johannes Berg [this message]
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=1294824413.3639.17.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=miles.lane@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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