On Wed, 20 Jul 2011, Pekka Enberg wrote: > So what exactly is the lockdep complaint above telling us? We're holding on to > l3->list_lock in cache_flusharray() (kfree path) but somehow we now entered > cache_alloc_refill() (kmalloc path!) and attempt to take the same lock or lock > in the same class. > > I am confused. How can that happen? I guess you need a slab with CFLGS_OFF_SLAB metadata management. Then slab does some recursive things doing allocations and free for metadata while allocating larger objects. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>