linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, david@kernel.org,
	lorenzo.stoakes@oracle.com, ziy@nvidia.com,
	baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
	npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
	baohua@kernel.org, lance.yang@linux.dev, pjw@kernel.org,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	linux-mm@kvack.org, stable@vger.kernel.org
Subject: Re: [Patch v2] mm/huge_memory: fix NULL pointer deference when splitting folio
Date: Thu, 20 Nov 2025 00:03:12 +0000	[thread overview]
Message-ID: <20251120000312.xasxdzmmztvp4spa@master> (raw)
In-Reply-To: <20251119235302.24773-1-richard.weiyang@gmail.com>

On Wed, Nov 19, 2025 at 11:53:02PM +0000, Wei Yang wrote:
>Commit c010d47f107f ("mm: thp: split huge page to any lower order
>pages") introduced an early check on the folio's order via
>mapping->flags before proceeding with the split work.
>
>This check introduced a bug: for shmem folios in the swap cache and
>truncated folios, the mapping pointer can be NULL. Accessing
>mapping->flags in this state leads directly to a NULL pointer
>dereference.
>
>This commit fixes the issue by moving the check for mapping != NULL
>before any attempt to access mapping->flags.
>
>Fixes: c010d47f107f ("mm: thp: split huge page to any lower order pages")
>Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>Cc: Zi Yan <ziy@nvidia.com>
>Cc: "David Hildenbrand (Red Hat)" <david@kernel.org>
>Cc: <stable@vger.kernel.org>
>
>---
>This patch is based on current mm-new, latest commit:
>
>    febb34c02328 dt-bindings: riscv: Add Svrsw60t59b extension description
>
>v2:
>  * just move folio->mapping ahead
>---
> mm/huge_memory.c | 22 ++++++++++------------
> 1 file changed, 10 insertions(+), 12 deletions(-)
>
>diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>index efea42d68157..4e9e920f306d 100644
>--- a/mm/huge_memory.c
>+++ b/mm/huge_memory.c
>@@ -3929,6 +3929,16 @@ static int __folio_split(struct folio *folio, unsigned int new_order,
> 	if (folio != page_folio(split_at) || folio != page_folio(lock_at))
> 		return -EINVAL;
> 
>+	/*
>+	 * 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;
>+

This one would have a conflict on direct cherry-pick to current master and
mm-stable.

But if I move this code before (folio != page_folio(split_at) ...), it could
be apply to mm-new and master/mm-stable smoothly.

Not sure whether this could make Andrew's life easier.

> 	if (new_order >= old_order)
> 		return -EINVAL;
> 
>@@ -3965,18 +3975,6 @@ static int __folio_split(struct folio *folio, unsigned int new_order,
> 		gfp_t gfp;
> 
> 		mapping = folio->mapping;
>-
>-		/* Truncated ? */
>-		/*
>-		 * TODO: add support for large shmem folio in swap cache.
>-		 * When shmem is in swap cache, mapping is NULL and
>-		 * folio_test_swapcache() is true.
>-		 */
>-		if (!mapping) {
>-			ret = -EBUSY;
>-			goto out;
>-		}
>-
> 		min_order = mapping_min_folio_order(folio->mapping);
> 		if (new_order < min_order) {
> 			ret = -EINVAL;
>-- 
>2.34.1

-- 
Wei Yang
Help you, Help me


  reply	other threads:[~2025-11-20  0:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 23:53 Wei Yang
2025-11-20  0:03 ` Wei Yang [this message]
2025-11-20  0:46   ` Andrew Morton
2025-11-20  0:49     ` Wei Yang
2025-11-20  0:03 ` Zi Yan
2025-11-20  6:07 ` Baolin Wang
2025-11-20  9:24 ` David Hildenbrand (Red Hat)

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=20251120000312.xasxdzmmztvp4spa@master \
    --to=richard.weiyang@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=lance.yang@linux.dev \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=npache@redhat.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=stable@vger.kernel.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