From: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>
To: Qi Zheng <qi.zheng@linux.dev>,
muchun.song@linux.dev, osalvador@suse.de, david@kernel.org,
akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Qi Zheng <zhengqi.arch@bytedance.com>,
stable@vger.kernel.org, Lance Yang <lance.yang@linux.dev>
Subject: Re: [PATCH 4/4] mm: hugetlb: respect cpuset restrictions for surplus allocations
Date: Tue, 3 Nov 2026 13:21:57 +0100 [thread overview]
Message-ID: <b1c86bc9-24e8-4c87-b2a7-2eefbdd96c12@gmail.com> (raw)
In-Reply-To: <d1e41a65970ced879715a73ce2607de7ad102fb2.1793692578.git.zhengqi.arch@bytedance.com>
On 11/3/26 9:01 AM, Qi Zheng wrote:
> From: Qi Zheng <zhengqi.arch@bytedance.com>
>
> Gigantic surplus allocations can escape the faulting task's cpuset.
> CMA and the contiguous allocator trust the supplied nodemask without
> checking the current cpuset.
>
> For example, a shared HugeTLB VMA has MPOL_BIND={0,1}, and T is a
> non-leader thread. With surplus allocation enabled and no eligible free
> HugeTLB folio, the following sequence can occur:
>
> CPU0 (cgroup v1 migration) CPU1 (thread T)
> ------------------------- ---------------
> cpuset_attach_task(..., T)
> T->mems_allowed = {0}
> /* Non-leader: skip
> mpol_rebind_mm(). */
> /* Fault; VMA policy is still {0,1}. */
> policy_nodemask()
> /* {0,1} intersects {0}. */
> nodemask = {0,1}
> hugetlb_cma_alloc_frozen_folio()
> /* node0 fails; node1 succeeds. */
>
> The 1 GiB folio is allocated on node1 despite T being restricted to node0.
>
> Intersect the interpreted policy with the current cpuset before surplus
> allocation, preserving MPOL_BIND and MPOL_PREFERRED_MANY fallback rules.
> Apply the restriction at the policy-aware entry point to preserve
> per-node pool management semantics.
>
> If the cpuset changes during allocation, rebuild the mask and revalidate
> any allocated folio against the current constraints. Keep it if it is
> still eligible: freeing an HVO-optimized folio can defer returning its
> range to CMA, so discarding a usable folio can cause a needless allocation
> failure. Only release the folio and allocate again if it is no longer
> eligible.
>
> Fixes: eb02f14c4a2b ("mm/hugetlb: allow overcommitting gigantic hugepages")
> Cc: stable@vger.kernel.org
> Reported-by: Lance Yang <lance.yang@linux.dev>
> Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
> ---
> mm/hugetlb.c | 38 +++++++++++++++++++++++++++++++-------
> 1 file changed, 31 insertions(+), 7 deletions(-)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index ce9c8e57b8e5c..6fd6e58ace869 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -2181,22 +2181,46 @@ struct folio *alloc_buddy_hugetlb_folio(struct hstate *h,
> gfp_t gfp_mask, struct mempolicy_interpreted *mpoli)
> {
> struct folio *folio = NULL;
> - nodemask_t *nodemask = mpoli->nodemask;
> + nodemask_t alloc_nodemask;
> + unsigned int cpuset_mems_cookie;
> +
> +retry:
> + cpuset_mems_cookie = read_mems_allowed_begin();
> + alloc_nodemask = cpuset_current_mems_allowed;
> + if (mpoli->mode == MPOL_BIND && mpoli->nodemask &&
> + nodes_intersects(*mpoli->nodemask, alloc_nodemask))
> + nodes_and(alloc_nodemask, alloc_nodemask, *mpoli->nodemask);
> +
> + if (folio) {
> + if (unlikely(read_mems_allowed_retry(cpuset_mems_cookie)))
> + goto retry;
> +
> + if (node_isset(folio_nid(folio), alloc_nodemask))
> + return folio;
> +
> + /* Balance free_huge_folio()'s decrement before caller accounting */
> + lruvec_stat_mod_folio(folio, NR_HUGETLB, pages_per_huge_page(h));
> + free_huge_folio(folio);
> + folio = NULL;
> + }
the page allocator only retries when the allocation fails, why does this
need to drop a folio that raced with a cpuset change? retrying only on
!folio would make this whole block go away, with the check at the end as:
if (!folio &&
unlikely(read_mems_allowed_retry(cpuset_mems_cookie)))
goto retry;
>
> if (mpoli->mode == MPOL_PREFERRED_MANY) {
> gfp_t gfp = gfp_mask & ~(__GFP_DIRECT_RECLAIM | __GFP_NOFAIL);
>
> + nodes_and(alloc_nodemask, alloc_nodemask, *mpoli->nodemask);
> folio = alloc_surplus_hugetlb_folio(h, gfp, mpoli->nid,
> - nodemask);
> + &alloc_nodemask);
>
> - /* Fallback to all nodes if page==NULL */
> - nodemask = NULL;
> + /* Fallback to all nodes allowed by the current cpuset */
> + alloc_nodemask = cpuset_current_mems_allowed;
> }
>
> - if (!folio) {
> + if (!folio)
> folio = alloc_surplus_hugetlb_folio(h, gfp_mask, mpoli->nid,
> - nodemask);
> - }
> + &alloc_nodemask);
> +
> + if (unlikely(read_mems_allowed_retry(cpuset_mems_cookie)))
> + goto retry;
>
> return folio;
> }
--
cheers,
jose a. p-a
prev parent reply other threads:[~2026-11-03 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 8:01 [PATCH 0/4] mm: hugetlb: fix some CMA-related issues Qi Zheng
2026-11-03 8:01 ` [PATCH 1/4] x86: hugetlb: disable default CMA reservations on 32-bit kernel Qi Zheng
2026-11-03 8:41 ` Muchun Song
2026-11-03 11:40 ` Jose A. Perez de Azpillaga
2026-11-03 8:01 ` [PATCH 2/4] mm: hugetlb: skip CMA allocations under PF_MEMALLOC_PIN Qi Zheng
2026-11-03 8:44 ` Muchun Song
2026-11-03 10:56 ` Muchun Song
2026-11-03 11:59 ` Jose A. Perez de Azpillaga
2026-11-03 8:01 ` [PATCH 3/4] mm: hugetlb: skip CMA when direct reclaim is disallowed Qi Zheng
2026-11-03 8:01 ` [PATCH 4/4] mm: hugetlb: respect cpuset restrictions for surplus allocations Qi Zheng
2026-11-03 12:21 ` Jose A. Perez de Azpillaga [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=b1c86bc9-24e8-4c87-b2a7-2eefbdd96c12@gmail.com \
--to=azpijr@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=qi.zheng@linux.dev \
--cc=stable@vger.kernel.org \
--cc=zhengqi.arch@bytedance.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
all inboxes | Powered by JetHome®