Re: [PATCH v2 1/2] mm/hugetlb: do not dissolve gigantic pages without runtime support

[Andrew Morton <akpm@linux-foundation.org>]

On Sun, 23 Aug 2026 12:40:51 +0800 Longlong Xia <xialonglong2025@163.com> wrote:

> From: Longlong Xia <xialonglong@kylinos.cn>
> 
> dissolve_free_hugetlb_folio() doesn't check
> hstate_is_gigantic_no_runtime(h) though remove_hugetlb_folio()/
> update_and_free_hugetlb_folio() silently bail for such folios, so it
> frees a still-listed folio and, on vmemmap restore failure, the
> add_hugetlb_folio() rollback corrupts the free list.
> 
> Fixes: 6eb4e88a6d27 ("hugetlb: create remove_hugetlb_page() to separate functionality")
> Assisted-by: Codex:gpt-5.6-sol
> Signed-off-by: Longlong Xia <xialonglong@kylinos.cn>

This doesn't carry an explicit cc:stable, as you mentioned in the cover
letter.  And that's OK - people often omit it.  Perhaps because the
-stable people backport every dang thing which has a Fixes:.  They've
been asked not to do that for MM.

Also, the changelogging doesn't provide reasons for backporting the
fix.  Please review Documentation/process/stable-kernel-rules.rst.  The
key thing is to include a description of the userspace-visible runtime
effects of the bug.

A reproducer, a Reported-by:, a Closes:, etc.  *something* to explain
to people why they should make this change to their kernel.

From the v1 review discussion it appears that this fix was inspired by
a Sashiko report?  Changelogging this detail would be helpful.


I asked Gemini to create a reproducer for this
(https://share.gemini.google/be2PvvOLw6kx) and it's very involved. 
Makes me suspect that nobody has hit this in real life?


Muchun's ack wasn't carried over from the v1 patch?


Thanks, I'll apply the patches (hoping for additional review) but at
this stage I'm not really sure *why* I"m applying them!


btw, there wasn't anything in the [0/N] cover letter which was usable
in a cover letter.  But that's OK - I'll split the series apart anyway
Because [1/1] is cc:stable so it will take a different path into
mainline, with different timing.


hm, anyway, that was lengthy.  Please send along a few additional words
telling people why we feel this should be backported?