Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Hahn <joshua.hahnjy@gmail.com>
To: Yichong Chen <chenyichong@uniontech.com>
Cc: Muchun Song <muchun.song@linux.dev>,
	Oscar Salvador <osalvador@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Andrew Barry <abarry@cray.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hugetlb: fix subpool release race
Date: Mon, 20 Jul 2026 07:31:29 -0700	[thread overview]
Message-ID: <20260720143130.516711-1-joshua.hahnjy@gmail.com> (raw)
In-Reply-To: <20260720085024.1392261-1-chenyichong@uniontech.com>

Hello Yichong, thank you for the patch!

> unlock_or_release_subpool() drops spool->lock before checking whether the
> subpool can be freed.  However, subpool_is_free() reads fields that are
> updated under spool->lock, including count, used_hpages and rsv_hpages.
> 
> Another thread can update those fields before the first thread evaluates
> subpool_is_free(), allowing both threads to observe the final freeable
> state and release the subpool.

I don't think that the race you are mentioning can be hit in practice (i.e.
there is no user-visible change for this) since two threads cannot actually
observe the freeable state at the same time.

subpool_is_free() does an early exit on spool->count so it will never reach
the inside if block and have two threads try to decrement the
spool->hstate and free the spool twice. I'm wondering if we need the Fixes
tag in this case.

I do think that this is not obvious though, so having the subpool_is_free
check inside the locked section makes sense to me too.

Reviewed-by: Joshua Hahn <joshua.hahnjy@gmail.com>

Have a great day!
Joshua

> Make the free decision while still holding spool->lock.  Keep the actual
> hugetlb_acct_memory() and kfree() calls after dropping the lock.

> Fixes: 90481622d757 ("hugepages: fix use after free bug in "quota" handling")
> Signed-off-by: Yichong Chen <chenyichong@uniontech.com>
> ---
>  mm/hugetlb.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index e319c6a00555..46ab702c0fc0 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -140,12 +140,14 @@ static inline bool subpool_is_free(struct hugepage_subpool *spool)
>  static inline void unlock_or_release_subpool(struct hugepage_subpool *spool,
>  						unsigned long irq_flags)
>  {
> -	spin_unlock_irqrestore(&spool->lock, irq_flags);
> +	bool free_subpool = subpool_is_free(spool);
>  
>  	/* If no pages are used, and no other handles to the subpool
>  	 * remain, give up any reservations based on minimum size and
>  	 * free the subpool */
> -	if (subpool_is_free(spool)) {
> +	spin_unlock_irqrestore(&spool->lock, irq_flags);
> +
> +	if (free_subpool) {
>  		if (spool->min_hpages != -1)
>  			hugetlb_acct_memory(spool->hstate,
>  						-spool->min_hpages);
> -- 
> 2.51.0


      reply	other threads:[~2026-07-20 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  8:50 [PATCH] hugetlb: fix subpool release race Yichong Chen
2026-07-20 14:31 ` Joshua Hahn [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=20260720143130.516711-1-joshua.hahnjy@gmail.com \
    --to=joshua.hahnjy@gmail.com \
    --cc=abarry@cray.com \
    --cc=akpm@linux-foundation.org \
    --cc=chenyichong@uniontech.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=david@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    /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