From: <dan.j.williams@intel.com>
To: John Groves <John@Groves.net>,
David Hildenbrand <david@kernel.org>,
"Oscar Salvador" <osalvador@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Cc: John Groves <John@Groves.net>, John Groves <jgroves@micron.com>,
"Darrick J . Wong" <djwong@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Gregory Price <gourry@gourry.net>,
Balbir Singh <bsingharora@gmail.com>,
Alistair Popple <apopple@nvidia.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <linux-cxl@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>,
Aravind Ramesh <arramesh@micron.com>,
"Ajay Joshi" <ajayjoshi@micron.com>,
John Groves <john@groves.net>
Subject: Re: [PATCH] mm/memremap: fix spurious large folio warning for FS-DAX
Date: Wed, 17 Dec 2025 15:59:08 -0800 [thread overview]
Message-ID: <694343cc7e89_1cf51003@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <20251217211310.98772-1-john@groves.net>
John Groves wrote:
> From: John Groves <John@Groves.net>
>
> This patch addresses a warning that I discovered while working on famfs,
> which is an fs-dax file system that virtually always does PMD faults
> (next famfs patch series coming after the holidays).
>
> However, XFS also does PMD faults in fs-dax mode, and it also triggers
> the warning. It takes some effort to get XFS to do a PMD fault, but
> instructions to reproduce it are below.
>
> The VM_WARN_ON_ONCE(folio_test_large(folio)) check in
> free_zone_device_folio() incorrectly triggers for MEMORY_DEVICE_FS_DAX
> when PMD (2MB) mappings are used.
>
> FS-DAX legitimately creates large file-backed folios when handling PMD
> faults. This is a core feature of FS-DAX that provides significant
> performance benefits by mapping 2MB regions directly to persistent
> memory. When these mappings are unmapped, the large folios are freed
> through free_zone_device_folio(), which triggers the spurious warning.
>
> The warning was introduced by commit that added support for large zone
> device private folios. However, that commit did not account for FS-DAX
> file-backed folios, which have always supported large (PMD-sized)
> mappings.
Oh, I was not copied on:
d245f9b4ab80 mm/zone_device: support large zone device private folios
...I should probably add myself as a reviewer to the MEMORY HOT(UN)PLUG
entry in MAINTAINERS at least for the mm/mememap.c bits.
Now, why is the warning there in the first place?
I.e. what is the risk of just doing this fixup:
diff --git a/mm/memremap.c b/mm/memremap.c
index 4c2e0d68eb27..63c6ab4fdf08 100644
--- a/mm/memremap.c
+++ b/mm/memremap.c
@@ -427,8 +427,6 @@ void free_zone_device_folio(struct folio *folio)
if (folio_test_anon(folio)) {
for (i = 0; i < nr; i++)
__ClearPageAnonExclusive(folio_page(folio, i));
- } else {
- VM_WARN_ON_ONCE(folio_test_large(folio));
}
/*
next prev parent reply other threads:[~2025-12-17 23:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 21:13 John Groves
2025-12-17 22:58 ` Alistair Popple
2025-12-19 0:03 ` Andrew Morton
2025-12-19 0:27 ` John Groves
2025-12-17 23:59 ` dan.j.williams [this message]
2025-12-18 3:11 ` Alistair Popple
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=694343cc7e89_1cf51003@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=John@Groves.net \
--cc=ajayjoshi@micron.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=arramesh@micron.com \
--cc=bsingharora@gmail.com \
--cc=david@kernel.org \
--cc=djwong@kernel.org \
--cc=gourry@gourry.net \
--cc=jgroves@micron.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
/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