From: Christoph Lameter <cl@linux.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org, Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dmitry Safonov <dsafonov@virtuozzo.com>,
Vladimir Davydov <vdavydov@virtuozzo.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Dave Gordon <david.s.gordon@intel.com>,
linux-mm@kvack.org
Subject: Re: [PATCH v3] mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock
Date: Tue, 9 Aug 2016 11:21:33 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1608091121070.12004@east.gentwo.org> (raw)
In-Reply-To: <1470759070-18743-1-git-send-email-chris@chris-wilson.co.uk>
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>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-08-09 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 14:46 [PATCH] " Chris Wilson
2016-08-09 15:17 ` Vladimir Davydov
2016-08-09 15:27 ` [PATCH v2] " Chris Wilson
2016-08-09 15:45 ` Vladimir Davydov
2016-08-09 15:52 ` Chris Wilson
2016-08-09 16:06 ` Vladimir Davydov
2016-08-09 16:11 ` [PATCH v3] " Chris Wilson
2016-08-09 16:21 ` Christoph Lameter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1608091121070.12004@east.gentwo.org \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=david.s.gordon@intel.com \
--cc=dsafonov@virtuozzo.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vdavydov@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox