From: Oscar Salvador <osalvador@suse.de>
To: Wupeng Ma <mawupeng1@huawei.com>
Cc: akpm@linux-foundation.org, mike.kravetz@oracle.com,
david@redhat.com, joshua.hahnjy@gmail.com, muchun.song@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: hugetlb: Fix incorrect fallback for subpool
Date: Mon, 28 Apr 2025 10:41:03 +0200 [thread overview]
Message-ID: <aA8_H-sNZh_sNBvF@localhost.localdomain> (raw)
In-Reply-To: <20250410062633.3102457-1-mawupeng1@huawei.com>
On Thu, Apr 10, 2025 at 02:26:33PM +0800, Wupeng Ma wrote:
> During our testing with hugetlb subpool enabled, we observe that
> hstate->resv_huge_pages may underflow into negative values. Root cause
> analysis reveals a race condition in subpool reservation fallback handling
> as follow:
>
> hugetlb_reserve_pages()
> /* Attempt subpool reservation */
> gbl_reserve = hugepage_subpool_get_pages(spool, chg);
>
> /* Global reservation may fail after subpool allocation */
> if (hugetlb_acct_memory(h, gbl_reserve) < 0)
> goto out_put_pages;
>
> out_put_pages:
> /* This incorrectly restores reservation to subpool */
> hugepage_subpool_put_pages(spool, chg);
>
> When hugetlb_acct_memory() fails after subpool allocation, the current
> implementation over-commits subpool reservations by returning the full
> 'chg' value instead of the actual allocated 'gbl_reserve' amount. This
> discrepancy propagates to global reservations during subsequent releases,
> eventually causing resv_huge_pages underflow.
>
> This problem can be trigger easily with the following steps:
> 1. reverse hugepage for hugeltb allocation
> 2. mount hugetlbfs with min_size to enable hugetlb subpool
> 3. alloc hugepages with two task(make sure the second will fail due to
> insufficient amount of hugepages)
> 4. with for a few seconds and repeat step 3 which will make
> hstate->resv_huge_pages to go below zero.
>
> To fix this problem, return corrent amount of pages to subpool during the
> fallback after hugepage_subpool_get_pages is called.
>
> Fixes: 1c5ecae3a93f ("hugetlbfs: add minimum size accounting to subpools")
> Signed-off-by: Wupeng Ma <mawupeng1@huawei.com>
> Tested-by: Joshua Hahn <joshua.hahnjy@gmail.com>
Reviewed-by: Oscar Salvador <osalvador@suse.de>
--
Oscar Salvador
SUSE Labs
prev parent reply other threads:[~2025-04-28 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 6:26 Wupeng Ma
2025-04-18 3:03 ` Andrew Morton
2025-04-18 8:46 ` Oscar Salvador
2025-04-28 8:41 ` Oscar Salvador [this message]
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=aA8_H-sNZh_sNBvF@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawupeng1@huawei.com \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
/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