From: Andrew Morton Date: Thu, 9 May 2013 23:57:19 +0000 (+1000) Subject: memcg-debugging-facility-to-access-dangling-memcgs-fix X-Git-Tag: next-20130521~1^2~130 X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=17791292677db8e573c134eea1ea87fe91f628b2;p=karo-tx-linux.git memcg-debugging-facility-to-access-dangling-memcgs-fix fix up Kconfig text Cc: Glauber Costa Signed-off-by: Andrew Morton --- diff --git a/init/Kconfig b/init/Kconfig index 076a6342bc76..a4516ebeadb1 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -940,14 +940,14 @@ config MEMCG_KMEM will ever exhaust kernel resources alone. config MEMCG_DEBUG_ASYNC_DESTROY - bool "Memory Resource Controller Debug assynchronous object destruction" + bool "Memory Resource Controller Debug asynchronous object destruction" depends on MEMCG_KMEM || MEMCG_SWAP default n help - When a memcg is destroyed, the memory - consumed by it may not be immediately freed. This is because when some - extensions are used, such as swap or kernel memory, objects can - outlive the group and hold a reference to it. + When a memcg is destroyed, the memory consumed by it may not be + immediately freed. This is because when some extensions are used, such + as swap or kernel memory, objects can outlive the group and hold a + reference to it. If this is the case, the dangling_memcgs file will show information about what are the memcgs still alive, and which references are still