From: Ackerley Tng <ackerleytng@google.com>
To: devnull+ackerleytng.google.com@kernel.org
Cc: ackerleytng@google.com, akpm@linux-foundation.org,
david@kernel.org, erdemaktas@google.com, fvdl@google.com,
joshua.hahnjy@gmail.com, jthoughton@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mawupeng1@huawei.com, muchun.song@linux.dev, nphamcs@gmail.com,
osalvador@suse.de, peterx@redhat.com, rientjes@google.com,
shakeel.butt@linux.dev, stable@vger.kernel.org,
vannapurve@google.com
Subject: [POC PATCH 0/3] Reproducers for hugetlb allocation failure issues
Date: Wed, 8 Jul 2026 15:22:10 -0700 [thread overview]
Message-ID: <cover.1783549129.git.ackerleytng@google.com> (raw)
In-Reply-To: <20260708-hugetlb-alloc-failure-fixes-v2-0-c7f27cbb462b@google.com>
Please see separate patches for details!
Ackerley Tng (3):
Reproducer for false restoration on shared HugeTLB mappings
Reproducer for subpool usage leak
Reproducer for allocation failure due to cgroup v2 memory limits
cgroup_v2_allocation_failure.c | 160 +++++++++++++++++++++++++++++++++
subpool_leak_max_size.sh | 71 +++++++++++++++
subpool_shared_leak.c | 29 ++++++
subpool_shared_leak.sh | 86 ++++++++++++++++++
4 files changed, 346 insertions(+)
create mode 100644 cgroup_v2_allocation_failure.c
create mode 100755 subpool_leak_max_size.sh
create mode 100644 subpool_shared_leak.c
create mode 100755 subpool_shared_leak.sh
--
2.55.0.795.g602f6c329a-goog
next prev parent reply other threads:[~2026-07-08 22:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 22:12 [PATCH v2 0/5] Fix bugs on HugeTLB folio allocation failure paths Ackerley Tng via B4 Relay
2026-07-08 22:12 ` [PATCH v2 1/5] mm: hugetlb: Track used_hpages when getting/putting pages from subpool Ackerley Tng via B4 Relay
2026-07-08 22:12 ` [PATCH v2 2/5] mm: hugetlb: Fix subpool usage leak on allocation failure Ackerley Tng via B4 Relay
2026-07-09 15:34 ` Joshua Hahn
2026-07-09 16:23 ` Ackerley Tng
2026-07-09 22:15 ` Ackerley Tng
2026-07-08 22:12 ` [PATCH v2 3/5] mm: hugetlb: Fix folio refcount mismatch on memcg charge failure Ackerley Tng via B4 Relay
2026-07-09 18:54 ` Joshua Hahn
2026-07-09 18:58 ` Joshua Hahn
2026-07-08 22:12 ` [PATCH v2 4/5] mm: hugetlb: Return -ENOSPC " Ackerley Tng via B4 Relay
2026-07-09 19:18 ` Joshua Hahn
2026-07-08 22:12 ` [PATCH v2 5/5] mm: hugetlb: Move memcg charge earlier to prevent reservation leak Ackerley Tng via B4 Relay
2026-07-08 22:22 ` Ackerley Tng [this message]
2026-07-08 22:22 ` [POC PATCH 1/3] Reproducer for false restoration on shared HugeTLB mappings Ackerley Tng
2026-07-08 22:22 ` [POC PATCH 2/3] Reproducer for subpool usage leak Ackerley Tng
2026-07-08 22:22 ` [POC PATCH 3/3] Reproducer for allocation failure due to cgroup v2 memory limits Ackerley Tng
2026-07-09 2:14 ` [PATCH v2 0/5] Fix bugs on HugeTLB folio allocation failure paths Ackerley Tng
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=cover.1783549129.git.ackerleytng@google.com \
--to=ackerleytng@google.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=devnull+ackerleytng.google.com@kernel.org \
--cc=erdemaktas@google.com \
--cc=fvdl@google.com \
--cc=joshua.hahnjy@gmail.com \
--cc=jthoughton@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawupeng1@huawei.com \
--cc=muchun.song@linux.dev \
--cc=nphamcs@gmail.com \
--cc=osalvador@suse.de \
--cc=peterx@redhat.com \
--cc=rientjes@google.com \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=vannapurve@google.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