On 04/24/2014 01:27 PM, Al Viro wrote: > On Thu, Apr 24, 2014 at 12:56:36PM -0400, Sasha Levin wrote: >> > Hi all, >> > >> > While fuzzing with trinity inside a KVM tools guest running the latest -next >> > kernel I've stumbled on the following: >> > [ 191.871535] kmem_cache_destroy (mm/slab_common.c:363) >> > [ 191.871535] dcookie_unregister (fs/dcookies.c:302 fs/dcookies.c:343) > So it's dcookie_exit() doing kmem_cache_destroy(dcookie_cache) while > some timer is active? > > Why does that code bother with destroying/creating that sucker dynamically? > Is there any point at all? I'm not sure about the dynamic allocation part, but I fear that if we just switch to using static allocations it'll hide the underlying issue that triggered this bug instead of fixing it. Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
