Message ID | 87a7rf55vy.fsf@concordia.ellerman.id.au (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Fri, 2018-06-29 at 00:42 +1000, Michael Ellerman wrote: > Kent, Jens, > > This looks like it might be related to the recent bioset changes? > > cheers > > Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes: > > On Tue, 2018-06-26 at 23:36 +1000, Michael Ellerman wrote: > >> Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes: > ... > > I was able to reproduce again with slub_debug=FZP and DEBUG_INFO enabled > > on 4.17.0-rc7-next-20180601, but not much traces other than the Oops stack trace > > Are you still testing on that revision? It's nearly a month old. > > Please try to reproduce on mainline or today's linux-next. Problem is not reproducible on 4.18.0-rc3 mainline and today's next kernel
diff --git a/mm/mempool.c b/mm/mempool.c index b54f2c20e5e0..6e23d7a119d4 100644 --- a/mm/mempool.c +++ b/mm/mempool.c @@ -508,6 +508,10 @@ EXPORT_SYMBOL(mempool_alloc_slab); void mempool_free_slab(void *element, void *pool_data) { struct kmem_cache *mem = pool_data; + + if (WARN_ON_ONCE(!mem)) + return; + kmem_cache_free(mem, element); } EXPORT_SYMBOL(mempool_free_slab);