From: Yang Shi <shy828301@gmail.com>
To: vbabka@suse.cz, kirill.shutemov@linux.intel.com,
willy@infradead.org, akpm@linux-foundation.org
Cc: shy828301@gmail.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [v3 PATCH 1/7] mm: khugepaged: check THP flag in hugepage_vma_check()
Date: Mon, 6 Jun 2022 14:44:08 -0700 [thread overview]
Message-ID: <20220606214414.736109-2-shy828301@gmail.com> (raw)
In-Reply-To: <20220606214414.736109-1-shy828301@gmail.com>
Currently the THP flag check in hugepage_vma_check() will fallthrough if
the flag is NEVER and VM_HUGEPAGE is set. This is not a problem for now
since all the callers have the flag checked before or can't be invoked if
the flag is NEVER.
However, the following patch will call hugepage_vma_check() in more
places, for example, page fault, so this flag must be checked in
hugepge_vma_check().
Signed-off-by: Yang Shi <shy828301@gmail.com>
---
mm/khugepaged.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mm/khugepaged.c b/mm/khugepaged.c
index 671ac7800e53..84b9cf4b9be9 100644
--- a/mm/khugepaged.c
+++ b/mm/khugepaged.c
@@ -458,6 +458,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma,
if (shmem_file(vma->vm_file))
return shmem_huge_enabled(vma);
+ if (!khugepaged_enabled())
+ return false;
+
/* THP settings require madvise. */
if (!(vm_flags & VM_HUGEPAGE) && !khugepaged_always())
return false;
--
2.26.3
next prev parent reply other threads:[~2022-06-06 21:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 21:44 [mm-unstable v3 PATCH 0/7] Cleanup transhuge_xxx helpers Yang Shi
2022-06-06 21:44 ` Yang Shi [this message]
2022-06-09 17:49 ` [v3 PATCH 1/7] mm: khugepaged: check THP flag in hugepage_vma_check() Zach O'Keefe
2022-06-10 7:09 ` Miaohe Lin
2022-06-06 21:44 ` [v3 PATCH 2/7] mm: thp: introduce transhuge_vma_size_ok() helper Yang Shi
2022-06-09 22:21 ` Zach O'Keefe
2022-06-10 0:08 ` Yang Shi
2022-06-10 0:51 ` Zach O'Keefe
2022-06-10 16:38 ` Yang Shi
2022-06-10 21:24 ` Yang Shi
2022-06-10 7:20 ` Miaohe Lin
2022-06-10 16:47 ` Yang Shi
2022-06-06 21:44 ` [v3 PATCH 3/7] mm: khugepaged: remove the redundant anon vma check Yang Shi
2022-06-09 23:23 ` Zach O'Keefe
2022-06-10 0:01 ` Yang Shi
2022-06-10 7:23 ` Miaohe Lin
2022-06-10 7:28 ` Miaohe Lin
2022-06-06 21:44 ` [v3 PATCH 4/7] mm: khugepaged: use transhuge_vma_suitable replace open-code Yang Shi
2022-06-10 1:51 ` Zach O'Keefe
2022-06-10 16:59 ` Yang Shi
2022-06-10 22:03 ` Yang Shi
2022-06-11 0:27 ` Zach O'Keefe
2022-06-11 3:25 ` Yang Shi
2022-06-11 21:43 ` Zach O'Keefe
2022-06-14 17:40 ` Yang Shi
2022-06-06 21:44 ` [v3 PATCH 5/7] mm: thp: kill transparent_hugepage_active() Yang Shi
2022-06-10 1:02 ` Zach O'Keefe
2022-06-10 17:02 ` Yang Shi
2022-06-13 15:06 ` Zach O'Keefe
2022-06-14 19:16 ` Yang Shi
2022-06-06 21:44 ` [v3 PATCH 6/7] mm: thp: kill __transhuge_page_enabled() Yang Shi
2022-06-10 2:22 ` Zach O'Keefe
2022-06-10 17:24 ` Yang Shi
2022-06-10 21:07 ` Yang Shi
2022-06-13 14:54 ` Zach O'Keefe
2022-06-14 18:51 ` Yang Shi
2022-06-14 23:55 ` Zach O'Keefe
2022-06-06 21:44 ` [v3 PATCH 7/7] mm: khugepaged: reorg some khugepaged helpers Yang Shi
2022-06-09 23:32 ` [mm-unstable v3 PATCH 0/7] Cleanup transhuge_xxx helpers Zach O'Keefe
2022-06-10 7:08 ` Miaohe Lin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220606214414.736109-2-shy828301@gmail.com \
--to=shy828301@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).