[Devel] [PATCH] ms/mm/slub.c: list_lock may not be held in some circumstances

From: David Rientjes Commit c65c1877bd68 ("slub: use lockdep_assert_held") incorrectly required that add_full() and remove_full() hold n->list_lock. The lock is only taken when kmem_cache_debug(s), since that's the only time it actually does anything. Require that the lock

Re: [Devel] [PATCH] ms/mm/slub.c: list_lock may not be held in some circumstances

On 11/15/2016 06:51 PM, Dmitry Safonov wrote: > From: David Rientjes > > Commit c65c1877bd68 ("slub: use lockdep_assert_held") incorrectly > required that add_full() and remove_full() hold n->list_lock. The lock > is only taken when kmem_cache_debug(s), since that's the

[Devel] [PATCH] ms/mm/slub.c: list_lock may not be held in some circumstances

From: David Rientjes Commit c65c1877bd68 ("slub: use lockdep_assert_held") incorrectly required that add_full() and remove_full() hold n->list_lock. The lock is only taken when kmem_cache_debug(s), since that's the only time it actually does anything. Require that the lock