linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Zi Yan <ziy@nvidia.com>, Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	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>,
	Miaohe Lin <linmiaohe@huawei.com>,
	Naoya Horiguchi <nao.horiguchi@gmail.com>,
	Wei Yang <richard.weiyang@gmail.com>,
	Balbir Singh <balbirs@nvidia.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] mm/huge_memory: change folio_split_supported() to folio_check_splittable()
Date: Wed, 26 Nov 2025 10:54:55 +0100	[thread overview]
Message-ID: <46d5090c-a6c5-41de-91c4-dacac58e1f9b@kernel.org> (raw)
In-Reply-To: <20251126035008.1919461-2-ziy@nvidia.com>

> -	/*
> -	 * Folios that just got truncated cannot get split. Signal to the
> -	 * caller that there was a race.
> -	 *
> -	 * TODO: this will also currently refuse shmem folios that are in the
> -	 * swapcache.
> -	 */
> -	if (!is_anon && !folio->mapping)
> -		return -EBUSY;
> -
>   	if (new_order >= old_order)
>   		return -EINVAL;
>   
> -	if (!folio_split_supported(folio, new_order, split_type, /* warn = */ true))
> -		return -EINVAL;
> -
> -	is_hzp = is_huge_zero_folio(folio);
> -	if (is_hzp) {
> -		pr_warn_ratelimited("Called split_huge_page for huge zero page\n");
> -		return -EBUSY;

As we are changing that case to a VM_WARN_ONCE(), is there some path 
where we might trigger that?

I'm wondering about the split_huge_pages_all() function in particular. I 
guess the "!folio_test_lru(folio)" would protect us?

Apart from that LGTM

Acked-by: David Hildenbrand (Red Hat) <david@kernel.org>

-- 
Cheers

David


  parent reply	other threads:[~2025-11-26  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  3:50 [PATCH v3 0/4] Improve folio split related functions Zi Yan
2025-11-26  3:50 ` [PATCH v3 1/4] mm/huge_memory: change folio_split_supported() to folio_check_splittable() Zi Yan
2025-11-26  4:14   ` Balbir Singh
2025-11-26 16:55     ` Zi Yan
2025-11-26  9:54   ` David Hildenbrand (Red Hat) [this message]
2025-11-26 16:59     ` Zi Yan
2025-11-27  5:23   ` Barry Song
2025-11-26  3:50 ` [PATCH v3 2/4] mm/huge_memory: replace can_split_folio() with direct refcount calculation Zi Yan
2025-11-26  9:56   ` David Hildenbrand (Red Hat)
2025-11-26 16:59     ` Zi Yan
2025-11-26  3:50 ` [PATCH v3 3/4] mm/huge_memory: make min_order_for_split() always return an order Zi Yan
2025-11-26  3:50 ` [PATCH v3 4/4] mm/huge_memory: fix folio split stats counting Zi Yan

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=46d5090c-a6c5-41de-91c4-dacac58e1f9b@kernel.org \
    --to=david@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbirs@nvidia.com \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=dev.jain@arm.com \
    --cc=lance.yang@linux.dev \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=nao.horiguchi@gmail.com \
    --cc=npache@redhat.com \
    --cc=richard.weiyang@gmail.com \
    --cc=ryan.roberts@arm.com \
    --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