From: Matthew Wilcox <willy@infradead.org>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: stricter check on THP migration entry
Date: Mon, 20 Jun 2022 05:48:54 +0100 [thread overview]
Message-ID: <Yq/8NonqNmMGAeJ2@casper.infradead.org> (raw)
In-Reply-To: <20220618073243.9423-1-linmiaohe@huawei.com>
On Sat, Jun 18, 2022 at 03:32:43PM +0800, Miaohe Lin wrote:
> When VM_BUG_ON check for THP migration entry, the existing code only check
> thp_migration_supported case, but not for !thp_migration_supported case.
> If !thp_migration_supported() and !pmd_present(), the original code may
> dead loop in theory. To make the VM_BUG_ON check more consistent, we need
> to catch both cases.
This patch makes no sense to me.
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> mm/memory.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/mm/memory.c b/mm/memory.c
> index fee2884481f2..6a9a17c7f58a 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -5043,10 +5043,9 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,
>
> barrier();
> if (unlikely(is_swap_pmd(vmf.orig_pmd))) {
> - VM_BUG_ON(thp_migration_supported() &&
> - !is_pmd_migration_entry(vmf.orig_pmd));
> - if (is_pmd_migration_entry(vmf.orig_pmd))
> - pmd_migration_entry_wait(mm, vmf.pmd);
> + VM_BUG_ON(!thp_migration_supported() ||
> + !is_pmd_migration_entry(vmf.orig_pmd));
> + pmd_migration_entry_wait(mm, vmf.pmd);
> return 0;
> }
> if (pmd_trans_huge(vmf.orig_pmd) || pmd_devmap(vmf.orig_pmd)) {
> --
> 2.23.0
>
>
next prev parent reply other threads:[~2022-06-20 4:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 7:32 Miaohe Lin
2022-06-20 4:48 ` Matthew Wilcox [this message]
2022-06-20 6:38 ` 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=Yq/8NonqNmMGAeJ2@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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