Re: [PATCH v3] mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock

From	Christoph Lameter <cl@linux.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH v3] mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock
Date	2016-08-09 18:30 +0200
Message-ID	<s4i4F-1wy-5@gated-at.bofh.it> (permalink)
References	<s4h8B-UE-11@gated-at.bofh.it> <s4hUZ-1tf-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, 9 Aug 2016, Chris Wilson wrote:

> With debugobjects enabled and using SLAB_DESTROY_BY_RCU, when a
> kmem_cache_node is destroyed the call_rcu() may trigger a slab
> allocation to fill the debug object pool (__debug_object_init:fill_pool).
> Everywhere but during kmem_cache_destroy(), discard_slab() is performed
> outside of the kmem_cache_node->list_lock and avoids a lockdep warning
> about potential recursion:

Acked-by: Christoph Lameter <cl@linux.com>

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[PATCH v2] mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock Chris Wilson <chris@chris-wilson.co.uk> - 2016-08-09 17:30 +0200
  Re: [PATCH v2] mm/slub: Run free_partial() outside of the  kmem_cache_node->list_lock Chris Wilson <chris@chris-wilson.co.uk> - 2016-08-09 18:00 +0200
  [PATCH v3] mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock Chris Wilson <chris@chris-wilson.co.uk> - 2016-08-09 18:20 +0200
    Re: [PATCH v3] mm/slub: Run free_partial() outside of the  kmem_cache_node->list_lock Christoph Lameter <cl@linux.com> - 2016-08-09 18:30 +0200

csiph-web