On Tue, 24 Mar 2015, David Rientjes wrote: > Mempools based on slab caches with object constructors are risky because > element allocation can happen either from the slab cache itself, meaning > the constructor is properly called before returning, or from the mempool > reserve pool, meaning the constructor is not called before returning, > depending on the allocation context. I don't think there is any problem. If the allocation is hapenning from the slab cache, the constructor is called from the slab sybsystem. If the allocation is hapenning from the mempool reserve, the constructor was called in the past (when the mempool reserve was refilled from the cache). So, in both cases, the object allocated frmo the mempool is constructed. Mikulas > For this reason, we should disallow creating mempools based on slab > caches that have object constructors. Callers of mempool_alloc() will > be responsible for properly initializing the returned element. > > Then, it doesn't matter if the element came from the slab cache or the > mempool reserved pool. > > The only occurrence of a mempool being based on a slab cache with an > object constructor in the tree is in fs/jfs/jfs_metapage.c. Remove it > and properly initialize the element in alloc_metapage(). > > At the same time, META_free is never used, so remove it as well. -- 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/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>