mm/page_owner: move config option to mm/Kconfig.debug

Move the PAGE_OWNER option from submenu "Compile-time checks and
compiler options" to dedicated submenu "Memory Debugging".

Link: http://lkml.kernel.org/r/20190120024254.6270-1-changbin.du@gmail.com
Signed-off-by: Changbin Du <changbin.du@gmail.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 48f5843..e6a7b01 100644 (file)
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -265,23 +265,6 @@ config UNUSED_SYMBOLS
          you really need it, and what the merge plan to the mainline kernel for
          your module is.
 
-config PAGE_OWNER
-       bool "Track page owner"
-       depends on DEBUG_KERNEL && STACKTRACE_SUPPORT
-       select DEBUG_FS
-       select STACKTRACE
-       select STACKDEPOT
-       select PAGE_EXTENSION
-       help
-         This keeps track of what call chain is the owner of a page, may
-         help to find bare alloc_page(s) leaks. Even if you include this
-         feature on your build, it is disabled in default. You should pass
-         "page_owner=on" to boot parameter in order to enable it. Eats
-         a fair amount of memory if enabled. See tools/vm/page_owner_sort.c
-         for user-space helper.
-
-         If unsure, say N.
-
 config DEBUG_FS
        bool "Debug Filesystem"
        help

diff --git a/mm/Kconfig.debug b/mm/Kconfig.debug
index 9a7b8b0..e3df921 100644 (file)
--- a/mm/Kconfig.debug
+++ b/mm/Kconfig.debug
@@ -39,6 +39,23 @@ config DEBUG_PAGEALLOC_ENABLE_DEFAULT
          Enable debug page memory allocations by default? This value
          can be overridden by debug_pagealloc=off|on.
 
+config PAGE_OWNER
+       bool "Track page owner"
+       depends on DEBUG_KERNEL && STACKTRACE_SUPPORT
+       select DEBUG_FS
+       select STACKTRACE
+       select STACKDEPOT
+       select PAGE_EXTENSION
+       help
+         This keeps track of what call chain is the owner of a page, may
+         help to find bare alloc_page(s) leaks. Even if you include this
+         feature on your build, it is disabled in default. You should pass
+         "page_owner=on" to boot parameter in order to enable it. Eats
+         a fair amount of memory if enabled. See tools/vm/page_owner_sort.c
+         for user-space helper.
+
+         If unsure, say N.
+
 config PAGE_POISONING
        bool "Poison pages after freeing"
        select PAGE_POISONING_NO_SANITY if HIBERNATION