thp: remove some code depend on CONFIG_NUMA

If NUMA is disabled, hpage is used as page pre-alloc, so there are two
cases for hpage:

- it is !NULL, means the page is not consumed otherwise,
- the page has been consumed

If NUMA is enabled, hpage is just used as alloc-fail indicator which is
not a real page, NULL means not fail triggered.

So, we can release the page only if !IS_ERR_OR_NULL

Signed-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: Hugh Dickins <hughd@google.com>
Cc: David Rientjes <rientjes@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index b1660e2d48ed3f02aa6ada1c931c0659801c6272..c7ce8a6fcf78bd8e7c8fd2192f9d46b0118acc07 100644 (file)
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -2372,11 +2372,8 @@ static void khugepaged_wait_work(void)
 
 static void khugepaged_loop(void)
 {
-       struct page *hpage;
+       struct page *hpage = NULL;
 
-#ifdef CONFIG_NUMA
-       hpage = NULL;
-#endif
        while (likely(khugepaged_enabled())) {
 #ifndef CONFIG_NUMA
                hpage = khugepaged_alloc_hugepage();
@@ -2390,10 +2387,9 @@ static void khugepaged_loop(void)
 #endif
 
                khugepaged_do_scan(&hpage);
-#ifndef CONFIG_NUMA
-               if (hpage)
+
+               if (!IS_ERR_OR_NULL(hpage))
                        put_page(hpage);
-#endif
 
                khugepaged_wait_work();
        }