From: Mike Kravetz <mike.kravetz@oracle.com>
To: Miaohe Lin <linmiaohe@huawei.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/hugetlb: Remove redundant VM_BUG_ON_PAGE on putback_active_hugepage()
Date: Mon, 8 Feb 2021 17:26:08 -0800 [thread overview]
Message-ID: <7e1cdef7-e3cd-79c1-c30c-5f5e9e9f85ac@oracle.com> (raw)
In-Reply-To: <20210208083739.33178-1-linmiaohe@huawei.com>
On 2/8/21 12:37 AM, Miaohe Lin wrote:
> PageHead(page) is implicitly checked in set_page_huge_active() via the
> PageHeadHuge(page) check. So remove this explicit one.
I do not disagree with the code change. However, this commit message
is not accurate. set_page_huge_active() no longer exists in the tree
you are changing. It was replaced with SetHPageMigratable. Also, the
VM_BUG_ON_PAGE(!PageHeadHuge(page), page) was removed in the process.
So, there is no redundant check.
However, a quick audit of calling code reveals that all callers know they
are operating on a hugetlb head page.
--
Mike Kravetz
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> mm/hugetlb.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 6cdb59d8f663..bbbe013a3a2d 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -5577,7 +5577,6 @@ bool isolate_huge_page(struct page *page, struct list_head *list)
>
> void putback_active_hugepage(struct page *page)
> {
> - VM_BUG_ON_PAGE(!PageHead(page), page);
> spin_lock(&hugetlb_lock);
> SetHPageMigratable(page);
> list_move_tail(&page->lru, &(page_hstate(page))->hugepage_activelist);
>
next prev parent reply other threads:[~2021-02-09 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 8:37 Miaohe Lin
2021-02-09 1:26 ` Mike Kravetz [this message]
2021-02-09 2:10 ` Miaohe Lin
2021-02-09 3:39 ` Mike Kravetz
2021-02-09 6:19 ` 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=7e1cdef7-e3cd-79c1-c30c-5f5e9e9f85ac@oracle.com \
--to=mike.kravetz@oracle.com \
--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