From: "Zach O'Keefe" <zokeefe@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yang Shi <shy828301@gmail.com>, linux-mm@kvack.org
Subject: Re: [PATCH] mm/khugepaged: check compound_order() in collapse_pte_mapped_thp()
Date: Wed, 21 Sep 2022 15:39:08 -0700 [thread overview]
Message-ID: <CAAa6QmRfWUNHtsS8P2cBDrT6hjyxrucU0FHE1x8kWW5SVDCEug@mail.gmail.com> (raw)
In-Reply-To: <20220921221043.547580-1-zokeefe@google.com>
On Wed, Sep 21, 2022 at 3:10 PM Zach O'Keefe <zokeefe@google.com> wrote:
>
> By the time we lock a page in collapse_pte_mapped_thp(), the page
> mapped by the address pushed onto the slot's .pte_mapped_thp[] array
> might have changed arbitrarily since we last looked at it. We
> revalidate that the page is still the head of a compound page, but we
> don't revalidate if the compound page is of order HPAGE_PMD_ORDER before
> applying rmap and page table updates.
>
> Since the kernel now supports large folios of arbitrary order, and since
> replacing page's pte mappings by a pmd mapping only makes sense for
> compound pages of order HPAGE_PMD_ORDER, revalidate that the compound
> order is indeed of order HPAGE_PMD_ORDER before proceeding.
>
> Suggested-by: Yang Shi <shy828301@gmail.com>
> Signed-off-by: Zach O'Keefe <zokeefe@google.com>
> ---
>
> Andrew, could you please take this into mm-unstable as a prerequisite
> patch for the "mm: add file/shmem support to MADV_COLLAPSE" series?
> Thank you.
>
> mm/khugepaged.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index 122cb72435e3..30f35d646f11 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -1448,6 +1448,11 @@ int collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr,
> goto drop_hpage;
> }
>
> + if (compound_order(hpage) != HPAGE_PMD_ORDER) {
> + result = SCAN_PAGE_COMPOUND;
> + goto drop_hpage;
> + }
> +
> result = find_pmd_or_thp_or_none(mm, haddr, &pmd);
> switch (result) {
> case SCAN_SUCCEED:
> --
> 2.37.3.998.g577e59143f-goog
>
Apologies, I forgot the relevant Link tag:
Link: https://lore.kernel.org/linux-mm/CAHbLzkon+2ky8v9ywGcsTUgXM_B35jt5NThYqQKXW2YV_GUacw@mail.gmail.com/
next prev parent reply other threads:[~2022-09-21 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 22:10 Zach O'Keefe
2022-09-21 22:39 ` Zach O'Keefe [this message]
2022-09-22 22:17 ` Zach O'Keefe
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=CAAa6QmRfWUNHtsS8P2cBDrT6hjyxrucU0FHE1x8kWW5SVDCEug@mail.gmail.com \
--to=zokeefe@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
/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