From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,wangkefeng.wang@huawei.com,vbabka@kernel.org,surenb@google.com,sunnanyong@huawei.com,stable@vger.kernel.org,ryan.roberts@arm.com,rppt@kernel.org,mhocko@suse.com,ljs@kernel.org,liam.howlett@oracle.com,david@kernel.org,baohua@kernel.org,tujinjiang@huawei.com,akpm@linux-foundation.org
Subject: + mm-huge_memory-fix-folio-isnt-locked-in-softleaf_to_folio-v4.patch added to mm-hotfixes-unstable branch
Date: Mon, 23 Mar 2026 12:33:26 -0700 [thread overview]
Message-ID: <20260323193327.3C301C4CEF7@smtp.kernel.org> (raw)
The patch titled
Subject: mm-huge_memory-fix-folio-isnt-locked-in-softleaf_to_folio-v4
has been added to the -mm mm-hotfixes-unstable branch. Its filename is
mm-huge_memory-fix-folio-isnt-locked-in-softleaf_to_folio-v4.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-huge_memory-fix-folio-isnt-locked-in-softleaf_to_folio-v4.patch
This patch will later appear in the mm-hotfixes-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via various
branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days
------------------------------------------------------
From: Jinjiang Tu <tujinjiang@huawei.com>
Subject: mm-huge_memory-fix-folio-isnt-locked-in-softleaf_to_folio-v4
Date: Sat, 21 Mar 2026 15:52:14 +0800
update function name and comments
Link: https://lkml.kernel.org/r/20260321075214.3305564-1-tujinjiang@huawei.com
Fixes: e9b61f19858a ("thp: reintroduce split_huge_page()")
Signed-off-by: Jinjiang Tu <tujinjiang@huawei.com>
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
Reviewed-by: Lorenzo Stoakes (Oracle) <ljs@kernel.org>
Cc: <stable@vger.kernel.org>
Cc: Barry Song <baohua@kernel.org>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Liam Howlett <liam.howlett@oracle.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Mike Rapoport <rppt@kernel.org>
Cc: Nanyong Sun <sunnanyong@huawei.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Vlastimil Babka <vbabka@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/leafops.h | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
--- a/include/linux/leafops.h~mm-huge_memory-fix-folio-isnt-locked-in-softleaf_to_folio-v4
+++ a/include/linux/leafops.h
@@ -363,10 +363,14 @@ static inline unsigned long softleaf_to_
return swp_offset(entry) & SWP_PFN_MASK;
}
-static inline void softleaf_migration_entry_check(softleaf_t entry,
- struct folio *folio)
+static inline void softleaf_migration_sync(softleaf_t entry,
+ struct folio *folio)
{
- /* See __split_folio_to_order() comment */
+ /*
+ * Ensure we do not race with split, which might alter tail pages into new
+ * folios and thus result in observing an unlocked folio.
+ * This matches the write barrier in __split_folio_to_order().
+ */
smp_rmb();
/*
@@ -388,7 +392,7 @@ static inline struct page *softleaf_to_p
VM_WARN_ON_ONCE(!softleaf_has_pfn(entry));
if (softleaf_is_migration(entry))
- softleaf_migration_entry_check(entry, page_folio(page));
+ softleaf_migration_sync(entry, page_folio(page));
return page;
}
@@ -405,7 +409,7 @@ static inline struct folio *softleaf_to_
VM_WARN_ON_ONCE(!softleaf_has_pfn(entry));
if (softleaf_is_migration(entry))
- softleaf_migration_entry_check(entry, folio);
+ softleaf_migration_sync(entry, folio);
return folio;
}
_
Patches currently in -mm which might be from tujinjiang@huawei.com are
mm-huge_memory-fix-folio-isnt-locked-in-softleaf_to_folio.patch
mm-huge_memory-fix-folio-isnt-locked-in-softleaf_to_folio-v4.patch
mm-hugetlb-fix-memory-offline-failure-due-to-hwpoisoned-file-hugetlb.patch
reply other threads:[~2026-03-23 19:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260323193327.3C301C4CEF7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=david@kernel.org \
--cc=liam.howlett@oracle.com \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=stable@vger.kernel.org \
--cc=sunnanyong@huawei.com \
--cc=surenb@google.com \
--cc=tujinjiang@huawei.com \
--cc=vbabka@kernel.org \
--cc=wangkefeng.wang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.