On 02/21/2013 03:00 AM, Tejun Heo wrote: > (cc'ing cgroup / memcg people and quoting whole body) > > Looks like something is going wrong with memcg cache destruction. > Glauber, any ideas? Also, can we please not use names as generic as > kmem_cache_destroy_work_func for something specific to memcg? How > about something like memcg_destroy_cache_workfn? > > Thanks.
Steffen, Is there any chance you could test that using SLAB instead of SLUB? I haven't manage to reproduce it yet, but I am working on some theories about why this is happening. If I could at least know if this is likely a cache problem vs a inner-memcg problem, that would help. The calltrace is not incredibly helpful, but it does indicate that the problem happens when freeing cache objects. -- 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/
