The patch titled Subject: mm/mempool: allow NULL `pool' pointer in mempool_destroy() has been removed from the -mm tree. Its filename was mm-mempool-allow-null-pool-pointer-in-mempool_destroy.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx> Subject: mm/mempool: allow NULL `pool' pointer in mempool_destroy() mempool_destroy() does not tolerate a NULL mempool_t pointer argument and performs a NULL-pointer dereference. This requires additional attention and effort from developers/reviewers and forces all mempool_destroy() callers to do a NULL check if (pool) mempool_destroy(pool); Or, otherwise, be invalid mempool_destroy() users. Tweak mempool_destroy() and NULL-check the pointer there. Proposed by Andrew Morton. Link: https://lkml.org/lkml/2015/6/8/583 Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx> Acked-by: David Rientjes <rientjes@xxxxxxxxxx> Cc: Julia Lawall <julia.lawall@xxxxxxx> Cc: Joe Perches <joe@xxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/mempool.c | 3 +++ 1 file changed, 3 insertions(+) diff -puN mm/mempool.c~mm-mempool-allow-null-pool-pointer-in-mempool_destroy mm/mempool.c --- a/mm/mempool.c~mm-mempool-allow-null-pool-pointer-in-mempool_destroy +++ a/mm/mempool.c @@ -150,6 +150,9 @@ static void *remove_element(mempool_t *p */ void mempool_destroy(mempool_t *pool) { + if (unlikely(!pool)) + return; + while (pool->curr_nr) { void *element = remove_element(pool); pool->free(element, pool->pool_data); _ Patches currently in -mm which might be from sergey.senozhatsky@xxxxxxxxx are -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html