From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Peter Chen <peter.chen@freescale.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org
Subject: Re: v3.9-rc1: swapper/0 [ INFO: possible circular locking dependency detected ]
Date: Thu, 07 Mar 2013 11:24:47 +0100 [thread overview]
Message-ID: <51386AEF.5090703@free-electrons.com> (raw)
In-Reply-To: <20130307080843.GG20470@nchen-desktop>
Hi Peter,
Le 07/03/2013 09:08, Peter Chen a écrit :
> On Wed, Mar 06, 2013 at 11:33:02AM +0100, Maxime Ripard wrote:
>> [ 2.149645] other info that might help us debug this:
>> [ 2.149645]
>> [ 2.157667] Possible unsafe locking scenario:
>> [ 2.157667]
>> [ 2.163598] CPU0 CPU1
>> [ 2.168134] ---- ----
>> [ 2.172667] lock(&(&cdev->lock)->rlock);
>> [ 2.176790] lock(&(&ci->lock)->rlock);
>> [ 2.183255] lock(&(&cdev->lock)->rlock);
>> [ 2.189893] lock(&(&ci->lock)->rlock);
>
> The precondition of above is the chipidea interrupt can be re-entered.
> But as far as I know, the same interrupt can't be re-entered at current
> system.
Yes, it seems to work quite fine anyway, but I'm not sure simply
ignoring this would be the right answer.
Maxime
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-03-07 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 10:33 v3.9-rc1: swapper/0 [ INFO: possible circular locking dependency detected ] Maxime Ripard
2013-03-06 13:43 ` Alexander Shishkin
2013-03-06 14:11 ` Maxime Ripard
2013-03-07 8:08 ` Peter Chen
2013-03-07 10:24 ` Maxime Ripard [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=51386AEF.5090703@free-electrons.com \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@freescale.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