From: Miaohe Lin <linmiaohe@huawei.com>
To: Mike Kravetz <mike.kravetz@oracle.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Cc: HORIGUCHI NAOYA <naoya.horiguchi@nec.com>,
Oscar Salvador <osalvador@suse.de>,
Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] hugetlb: do not demote poisoned hugetlb pages
Date: Tue, 8 Mar 2022 21:43:48 +0800 [thread overview]
Message-ID: <6ba788b3-901e-d740-2575-bc652461187b@huawei.com> (raw)
In-Reply-To: <20220307215707.50916-1-mike.kravetz@oracle.com>
On 2022/3/8 5:57, Mike Kravetz wrote:
> It is possible for poisoned hugetlb pages to reside on the free lists.
> The huge page allocation routines which dequeue entries from the free
> lists make a point of avoiding poisoned pages. There is no such check
> and avoidance in the demote code path.
>
> If a hugetlb page on the is on a free list, poison will only be set in
> the head page rather then the page with the actual error. If such a
> page is demoted, then the poison flag may follow the wrong page. A page
> without error could have poison set, and a page with poison could not
> have the flag set.
>
> Check for poison before attempting to demote a hugetlb page. Also,
> return -EBUSY to the caller if only poisoned pages are on the free list.
>
> Fixes: 8531fc6f52f5 ("hugetlb: add hugetlb demote page support")
> Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
> Cc: <stable@vger.kernel.org>
> ---
> mm/hugetlb.c | 17 ++++++++++-------
> 1 file changed, 10 insertions(+), 7 deletions(-)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index b34f50156f7e..f8ca7cca3c1a 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -3475,7 +3475,6 @@ static int demote_pool_huge_page(struct hstate *h, nodemask_t *nodes_allowed)
> {
> int nr_nodes, node;
> struct page *page;
> - int rc = 0;
>
> lockdep_assert_held(&hugetlb_lock);
>
> @@ -3486,15 +3485,19 @@ static int demote_pool_huge_page(struct hstate *h, nodemask_t *nodes_allowed)
> }
>
> for_each_node_mask_to_free(h, nr_nodes, node, nodes_allowed) {
> - if (!list_empty(&h->hugepage_freelists[node])) {
> - page = list_entry(h->hugepage_freelists[node].next,
> - struct page, lru);
> - rc = demote_free_huge_page(h, page);
> - break;
> + list_for_each_entry(page, &h->hugepage_freelists[node], lru) {
> + if (PageHWPoison(page))
> + continue;
> +
> + return demote_free_huge_page(h, page);
It seems this patch is not ideal. Memory failure can hit the hugetlb page anytime without
holding the hugetlb_lock. So the page might become HWPoison just after the check. But this
patch should have handled the common case. Many thanks for your work. :)
> }
> }
>
> - return rc;
> + /*
> + * Only way to get here is if all pages on free lists are poisoned.
> + * Return -EBUSY so that caller will not retry.
> + */
> + return -EBUSY;
> }
>
> #define HSTATE_ATTR_RO(_name) \
>
next prev parent reply other threads:[~2022-03-08 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 21:57 Mike Kravetz
2022-03-08 13:43 ` Miaohe Lin [this message]
2022-03-16 22:31 ` Mike Kravetz
2022-03-17 1:57 ` Miaohe Lin
2022-03-18 11:31 ` HORIGUCHI NAOYA(堀口 直也)
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=6ba788b3-901e-d740-2575-bc652461187b@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=stable@vger.kernel.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