From: Andrew Morton Date: Wed, 20 Mar 2013 04:07:31 +0000 (+1100) Subject: memcg-debugging-facility-to-access-dangling-memcgs-fix X-Git-Tag: next-20130321~2^2~307 X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=7f31e7b98a9f00b73638fa951ed7cad9c6a73e08;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 e1610b5eed53..5aebe3d6ea74 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -928,14 +928,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