On Wed, Jan 15, 2014 at 3:46 PM, Lothar Waßmann <LW@xxxxxxxxxxxxxxxxxxx> wrote: > Hi, > > Dong Aisheng wrote: >> On Mon, Jan 13, 2014 at 8:04 PM, Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: >> > On Thu, Dec 26, 2013 at 03:58:20PM +0800, Dong Aisheng wrote: >> >> > It's strange that this issue did not happen on kernel 3.10.17 with the same >> >> > code. 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. >> > >> > No, lockdep also doesn't know only that one line can take this lock. >> > Lockdep only knows a lock is taken from IRQ context, and disabling one >> > line still allows IRQs to happen and therefore it yells. >> >> Okay, thanks for the information. >> If that, kernel 3.10.17 has the same code, do you know why it does not trigger >> such lockdep error? >> > compiled with CONFIG_LOCKDEP disabled? > I did compile with LOCKDEP enabled. See below for a part of my .config CONFIG_DEBUG_SPINLOCK=y CONFIG_DEBUG_MUTEXES=y CONFIG_DEBUG_LOCK_ALLOC=y CONFIG_PROVE_LOCKING=y CONFIG_LOCKDEP=y # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_LOCKDEP is not set CONFIG_TRACE_IRQFLAGS=y CONFIG_DEBUG_ATOMIC_SLEEP=y That's why i think it's strange. Regards Dong Aisheng > > Lothar Waßmann > -- > ___________________________________________________________ > > Ka-Ro electronics GmbH | Pascalstraße 22 | D - 52076 Aachen > Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10 > Geschäftsführer: Matthias Kaussen > Handelsregistereintrag: Amtsgericht Aachen, HRB 4996 > > www.karo-electronics.de | info@xxxxxxxxxxxxxxxxxxx > ___________________________________________________________ -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
