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

Signed-off-by: Changbin Du <[email protected]>
---
 lib/Kconfig.debug | 17 -----------------
 mm/Kconfig.debug  | 17 +++++++++++++++++
 2 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index d4df5b24d75e..e43cfdc86fd6 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -266,23 +266,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 9a7b8b049d04..e3df921208c0 100644
--- 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
-- 
2.17.1

Reply via email to