From: Andrew Morton <akpm@linux-foundation.org>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: david@kernel.org, lorenzo.stoakes@oracle.com, riel@surriel.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, harry.yoo@oracle.com,
jannh@google.com, ziy@nvidia.com, gavinguo@igalia.com,
baolin.wang@linux.alibaba.com, linux-mm@kvack.org,
Lance Yang <lance.yang@linux.dev>,
stable@vger.kernel.org
Subject: Re: [Patch v2] mm/huge_memory: fix early failure try_to_migrate() when split huge pmd for shared thp
Date: Wed, 4 Feb 2026 19:13:09 -0800 [thread overview]
Message-ID: <20260204191309.5c61a11ddfbb71f6a1672c12@linux-foundation.org> (raw)
In-Reply-To: <20260205030421.zz72iie5bwvgxlsj@master>
On Thu, 5 Feb 2026 03:04:21 +0000 Wei Yang <richard.weiyang@gmail.com> wrote:
> >> Cc: Gavin Guo <gavinguo@igalia.com>
> >> Cc: "David Hildenbrand (Red Hat)" <david@kernel.org>
> >> Cc: Zi Yan <ziy@nvidia.com>
> >> Cc: Baolin Wang <baolin.wang@linux.alibaba.com>
> >> Cc: Lance Yang <lance.yang@linux.dev>
> >> Cc: <stable@vger.kernel.org>
> >
> >Why cc:stable? In other words, what is the userspace-visible runtime
> >effect of this bug?
>
> On memory pressure or failure, we would try to split folio to reclaim or limit
> bad memory. If failed to split it, we will leave some memory unusable.
>
> I would put this in change log, if it looks good to you.
>
> As David mentioned some change in comment and change log, do you prefer a v3?
v3 would be good please. If the patch(set) was large and had been
under test for significant time then I think a delta is preferable.
But that isn't the case here.
prev parent reply other threads:[~2026-02-05 3:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 0:42 Wei Yang
2026-02-04 2:03 ` Baolin Wang
2026-02-04 2:22 ` Zi Yan
2026-02-04 3:12 ` Lance Yang
2026-02-04 9:41 ` Gavin Guo
2026-02-04 19:36 ` David Hildenbrand (arm)
2026-02-04 20:02 ` Zi Yan
2026-02-04 20:43 ` David Hildenbrand (arm)
2026-02-05 2:59 ` Wei Yang
2026-02-04 19:42 ` Andrew Morton
2026-02-05 3:04 ` Wei Yang
2026-02-05 3:13 ` 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=20260204191309.5c61a11ddfbb71f6a1672c12@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=gavinguo@igalia.com \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=lance.yang@linux.dev \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=richard.weiyang@gmail.com \
--cc=riel@surriel.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.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