From: Andrew Morton <akpm@linux-foundation.org>
To: Hongfu Li <hongfu.li@linux.dev>
Cc: muchun.song@linux.dev, osalvador@suse.de, david@kernel.org,
steven.sistare@oracle.com, vivek.kasireddy@intel.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Hongfu Li <lihongfu@kylinos.cn>
Subject: Re: [PATCH] mm/hugetlb: fix resv_huge_pages double decrement in memfd error path
Date: Wed, 26 Aug 2026 19:47:59 -0700 [thread overview]
Message-ID: <20260826194759.88487180eebf728c1df08f14@linux-foundation.org> (raw)
In-Reply-To: <20260825021013.25672-1-hongfu.li@linux.dev>
On Tue, 25 Aug 2026 10:10:13 +0800 Hongfu Li <hongfu.li@linux.dev> wrote:
> From: Hongfu Li <lihongfu@kylinos.cn>
>
> alloc_hugetlb_folio_reserve() decrements h->resv_huge_pages when
> dequeuing a folio, but unlike the use_global_reservation handling in
> hugetlb_alloc_folio(), it does not set HPageRestoreReserve on the folio.
>
> Its sole caller memfd_alloc_folio() pre-allocates a reservation via
> hugetlb_reserve_pages() before allocating. When hugetlb_add_to_page_cache()
> fails, folio_put() drops the folio without HPageRestoreReserve set, so
> free_huge_folio() does not restore the reservation. The subsequent
> hugetlb_unreserve_pages() on the err_unresv path decrements the counter
> a second time, leaving resv_huge_pages off by one for every failed
> allocation.
>
> Set HPageRestoreReserve when consuming the reservation in
> alloc_hugetlb_folio_reserve(). On the error path, free_huge_folio() then
> restores the reservation before hugetlb_unreserve_pages() releases it.
> The success path is unaffected, as hugetlb_add_to_page_cache() clears
> the flag once the folio is added to the page cache.
>
> ...
>
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -2178,8 +2178,10 @@ struct folio *alloc_hugetlb_folio_reserve(struct hstate *h, int preferred_nid,
>
> folio = dequeue_hugetlb_folio_nodemask(h, gfp_mask, preferred_nid,
> nmask);
> - if (folio)
> + if (folio) {
> + folio_set_hugetlb_restore_reserve(folio);
> h->resv_huge_pages--;
> + }
>
> spin_unlock_irq(&hugetlb_lock);
> return folio;
Thanks. I pasted an AI-generated test case which might demonstrate
this bug. Requires fault-injection so I won't add cc:stable.
Also, Sashiko might have found an accounting issue in the nearby code
(Sashiko doesn't like hugetlb.c):
https://sashiko.dev/#/patchset/20260825021013.25672-1-hongfu.li@linux.dev
#define _GNU_SOURCE
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <sys/mman.h>
#include <linux/memfd.h>
/* Read resv_hugepages from sysfs */
static long get_resv_hugepages(void) {
FILE *f = fopen("/sys/kernel/mm/hugepages/hugepages-2048kB/resv_hugepages", "r");
if (!f) return -1;
long val = -1;
fscanf(f, "%ld", &val);
fclose(f);
return val;
}
int main(void) {
long orig_resv = get_resv_hugepages();
printf("[1] Initial resv_hugepages: %ld\n", orig_resv);
/* Enable fail_function for hugetlb_add_to_page_cache via debugfs */
system("echo hugetlb_add_to_page_cache > /sys/kernel/debug/fail_function/inject");
system("echo 100 > /sys/kernel/debug/fail_function/probability");
/* Create memfd and attempt write to allocate hugetlb folio */
int fd = memfd_create("test_memfd", MFD_HUGETLB);
if (fd >= 0) {
/* Force allocation path which triggers memfd_alloc_folio() */
ftruncate(fd, 2 * 1024 * 1024);
write(fd, "a", 1);
close(fd);
}
/* Disable error injection */
system("echo > /sys/kernel/debug/fail_function/inject");
long post_resv = get_resv_hugepages();
printf("[2] Post-failure resv_hugepages: %ld\n", post_resv);
if (post_resv < orig_resv) {
printf("[!] BUG DEMONSTRATED: resv_hugepages double-decremented by %ld!\n",
orig_resv - post_resv);
}
return 0;
}
prev parent reply other threads:[~2026-08-27 2:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 2:10 [PATCH] mm/hugetlb: fix resv_huge_pages double decrement in memfd error path Hongfu Li
2026-08-25 5:42 ` Muchun Song
2026-08-27 2:47 ` Andrew Morton [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=20260826194759.88487180eebf728c1df08f14@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hongfu.li@linux.dev \
--cc=lihongfu@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=steven.sistare@oracle.com \
--cc=vivek.kasireddy@intel.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