From: Wei Yang <richard.weiyang@gmail.com>
To: Zi Yan <ziy@nvidia.com>
Cc: linmiaohe@huawei.com, david@redhat.com, jane.chu@oracle.com,
kernel@pankajraghav.com,
syzbot+e6367ea2fdab6ed46056@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, akpm@linux-foundation.org,
mcgrof@kernel.org, nao.horiguchi@gmail.com,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Wei Yang <richard.weiyang@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [PATCH v2 1/3] mm/huge_memory: do not change split_huge_page*() target order silently.
Date: Thu, 16 Oct 2025 07:31:54 +0000 [thread overview]
Message-ID: <20251016073154.6vfydmo6lnvgyuzz@master> (raw)
In-Reply-To: <20251016033452.125479-2-ziy@nvidia.com>
On Wed, Oct 15, 2025 at 11:34:50PM -0400, Zi Yan wrote:
>Page cache folios from a file system that support large block size (LBS)
>can have minimal folio order greater than 0, thus a high order folio might
>not be able to be split down to order-0. Commit e220917fa507 ("mm: split a
>folio in minimum folio order chunks") bumps the target order of
>split_huge_page*() to the minimum allowed order when splitting a LBS folio.
>This causes confusion for some split_huge_page*() callers like memory
>failure handling code, since they expect after-split folios all have
>order-0 when split succeeds but in really get min_order_for_split() order
>folios.
>
>Fix it by failing a split if the folio cannot be split to the target order.
>Rename try_folio_split() to try_folio_split_to_order() to reflect the added
>new_order parameter. Remove its unused list parameter.
>
>Fixes: e220917fa507 ("mm: split a folio in minimum folio order chunks")
>[The test poisons LBS folios, which cannot be split to order-0 folios, and
>also tries to poison all memory. The non split LBS folios take more memory
>than the test anticipated, leading to OOM. The patch fixed the kernel
>warning and the test needs some change to avoid OOM.]
>Reported-by: syzbot+e6367ea2fdab6ed46056@syzkaller.appspotmail.com
>Closes: https://lore.kernel.org/all/68d2c943.a70a0220.1b52b.02b3.GAE@google.com/
>Signed-off-by: Zi Yan <ziy@nvidia.com>
>Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
>Reviewed-by: Pankaj Raghav <p.raghav@samsung.com>
Do we want to cc stable?
>---
> include/linux/huge_mm.h | 55 +++++++++++++++++------------------------
> mm/huge_memory.c | 9 +------
> mm/truncate.c | 6 +++--
> 3 files changed, 28 insertions(+), 42 deletions(-)
>
>diff --git a/include/linux/huge_mm.h b/include/linux/huge_mm.h
>index c4a811958cda..3d9587f40c0b 100644
>--- a/include/linux/huge_mm.h
>+++ b/include/linux/huge_mm.h
>@@ -383,45 +383,30 @@ static inline int split_huge_page_to_list_to_order(struct page *page, struct lis
> }
>
> /*
>- * try_folio_split - try to split a @folio at @page using non uniform split.
>+ * try_folio_split_to_order - try to split a @folio at @page to @new_order using
>+ * non uniform split.
> * @folio: folio to be split
>- * @page: split to order-0 at the given page
>- * @list: store the after-split folios
>+ * @page: split to @order at the given page
split to @new_order?
>+ * @new_order: the target split order
> *
>- * Try to split a @folio at @page using non uniform split to order-0, if
>- * non uniform split is not supported, fall back to uniform split.
>+ * Try to split a @folio at @page using non uniform split to @new_order, if
>+ * non uniform split is not supported, fall back to uniform split. After-split
>+ * folios are put back to LRU list. Use min_order_for_split() to get the lower
>+ * bound of @new_order.
We removed min_order_for_split() here right?
> *
> * Return: 0: split is successful, otherwise split failed.
> */
>-static inline int try_folio_split(struct folio *folio, struct page *page,
>- struct list_head *list)
>+static inline int try_folio_split_to_order(struct folio *folio,
>+ struct page *page, unsigned int new_order)
> {
>- int ret = min_order_for_split(folio);
>-
>- if (ret < 0)
>- return ret;
>-
>- if (!non_uniform_split_supported(folio, 0, false))
>- return split_huge_page_to_list_to_order(&folio->page, list,
>- ret);
>- return folio_split(folio, ret, page, list);
>+ if (!non_uniform_split_supported(folio, new_order, /* warns= */ false))
>+ return split_huge_page_to_list_to_order(&folio->page, NULL,
>+ new_order);
>+ return folio_split(folio, new_order, page, NULL);
> }
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-10-16 7:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 3:34 [PATCH v2 0/3] Do not change split folio target order Zi Yan
2025-10-16 3:34 ` [PATCH v2 1/3] mm/huge_memory: do not change split_huge_page*() target order silently Zi Yan
2025-10-16 7:31 ` Wei Yang [this message]
2025-10-16 14:32 ` Zi Yan
2025-10-16 20:59 ` Andrew Morton
2025-10-17 1:03 ` Zi Yan
2025-10-17 9:06 ` Lorenzo Stoakes
2025-10-17 9:10 ` Lorenzo Stoakes
2025-10-17 14:16 ` Zi Yan
2025-10-17 14:32 ` Lorenzo Stoakes
2025-10-18 0:05 ` Andrew Morton
2025-10-17 1:01 ` Wei Yang
2025-10-16 3:34 ` [PATCH v2 2/3] mm/memory-failure: improve large block size folio handling Zi Yan
2025-10-17 9:33 ` Lorenzo Stoakes
2025-10-20 20:09 ` Zi Yan
2025-10-17 19:11 ` Yang Shi
2025-10-20 19:46 ` Zi Yan
2025-10-20 23:41 ` Yang Shi
2025-10-21 1:23 ` Zi Yan
2025-10-21 15:44 ` David Hildenbrand
2025-10-21 15:55 ` Zi Yan
2025-10-21 18:28 ` David Hildenbrand
2025-10-21 18:57 ` Zi Yan
2025-10-21 19:07 ` Yang Shi
2025-10-22 6:39 ` Miaohe Lin
2025-10-16 3:34 ` [PATCH v2 3/3] mm/huge_memory: fix kernel-doc comments for folio_split() and related Zi Yan
2025-10-17 9:20 ` Lorenzo Stoakes
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=20251016073154.6vfydmo6lnvgyuzz@master \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=jane.chu@oracle.com \
--cc=kernel@pankajraghav.com \
--cc=lance.yang@linux.dev \
--cc=linmiaohe@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mcgrof@kernel.org \
--cc=nao.horiguchi@gmail.com \
--cc=npache@redhat.com \
--cc=p.raghav@samsung.com \
--cc=ryan.roberts@arm.com \
--cc=syzbot+e6367ea2fdab6ed46056@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).