mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: Longlong Xia <xialonglong2025@163.com>
Cc: osalvador@suse.de, akpm@linux-foundation.org, david@kernel.org,
	mike.kravetz@oracle.com, mhocko@suse.com, linmiaohe@huawei.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	xialonglong@kylinos.cn
Subject: Re: [PATCH v2 1/2] mm/hugetlb: do not dissolve gigantic pages without runtime support
Date: Fri, 28 Aug 2026 14:41:51 +0800	[thread overview]
Message-ID: <E654A716-5F59-4B7B-B402-17B1A776D541@linux.dev> (raw)
In-Reply-To: <20260823044118.1097121-2-xialonglong2025@163.com>



> On Aug 23, 2026, at 12:40, 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>

Again.

Acked-by: Muchun Song <muchun.song@linux.dev>

Thanks.


  parent reply	other threads:[~2026-08-28  6:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23  4:40 [PATCH v2 0/2] mm/hugetlb: " Longlong Xia
2026-08-23  4:40 ` [PATCH v2 1/2] mm/hugetlb: do not " Longlong Xia
2026-08-28  5:22   ` Andrew Morton
2026-08-28  6:41   ` Muchun Song [this message]
2026-08-23  4:40 ` [PATCH v2 2/2] mm/hugetlb: warn instead of silently bailing " Longlong Xia
2026-08-28  6:42   ` Muchun Song

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=E654A716-5F59-4B7B-B402-17B1A776D541@linux.dev \
    --to=muchun.song@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=mike.kravetz@oracle.com \
    --cc=osalvador@suse.de \
    --cc=xialonglong2025@163.com \
    --cc=xialonglong@kylinos.cn \
    /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®