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. 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. > --- -- 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
