On 20/06/13 13:57, Mark Jackson wrote: > Just mounted a JFFS2 partition (held in NOR flash on a custom AM335x > CPU board), and I always get the following:- > > [ 3.864244] > [ 3.865851] ====================================================== > [ 3.872359] [ INFO: possible circular locking dependency detected ] > [ 3.878968] 3.10.0-rc4-00172-gf31c62e-dirty #249 Not tainted > [ 3.884926] ------------------------------------------------------- > [ 3.891526] rcS/507 is trying to acquire lock: > [ 3.896206] (&mm->mmap_sem){++++++}, at: [<c00b42c8>] > might_fault+0x3c/0x94 > [ 3.903684] > [ 3.903684] but task is already holding lock: > [ 3.909826] (&f->sem){+.+.+.}, at: [<c016f208>] jffs2_readdir+0x40/0x1b0 > [ 3.917021] > [ 3.917021] which lock already depends on the new lock.
Looks like I reported something similar earlier this year:- http://lists.infradead.org/pipermail/linux-mtd/2013-February/045888.html And I also found this going back to 3.0.18:- http://www.spinics.net/lists/linux-rt-users/msg07617.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/