linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b29396@freescale.com (Dong Aisheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] mmc: sdhci: fix lockdep error on tunning routine
Date: Tue, 24 Dec 2013 10:05:24 +0800	[thread overview]
Message-ID: <20131224020521.GA23230@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <20131223122315.GJ26070@S2101-09.ap.freescale.net>

On Mon, Dec 23, 2013 at 08:23:17PM +0800, Shawn Guo wrote:
> On Mon, Dec 23, 2013 at 07:13:04PM +0800, Dong Aisheng wrote:
> > It's strange that this issue did not happen on kernel 3.10.17 with the same
> > code.
> 
> Probably just because you did not turn on CONFIG_PROVE_LOCKING on your
> 3.10.17 kennel.
> 

I did turn it on for the test.

Regards
Dong Aisheng

> Shawn
> 
> > And looking at the code, before call spin_lock we already disable the mmc
> > controller irq, per on my understanding, the deadlock given by lockdep may not
> > be able to happen(pls fix me if wrong).
> > May the lockdep not track the specific irq disable?
> > Copy lockdep guy to comment.
> > ---
> 

  reply	other threads:[~2013-12-24  2:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23 11:13 [PATCH 1/1] mmc: sdhci: fix lockdep error on tunning routine Dong Aisheng
2013-12-23 12:23 ` Shawn Guo
2013-12-24  2:05   ` Dong Aisheng [this message]
2013-12-26  7:58 ` Dong Aisheng
2014-01-13 10:32   ` Dong Aisheng
2014-01-13 12:04   ` Peter Zijlstra
2014-01-15  7:19     ` Dong Aisheng
2014-01-15  7:46       ` Lothar Waßmann
2014-01-15  8:44         ` Dong Aisheng
2014-01-15 10:09       ` Peter Zijlstra
2014-01-15 10:27         ` Dong Aisheng

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=20131224020521.GA23230@shlinux2.ap.freescale.net \
    --to=b29396@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).