From: Alistair Popple <apopple@nvidia.com>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, Alistair Popple <apopple@nvidia.com>,
gerald.schaefer@linux.ibm.com, dan.j.williams@intel.com,
jgg@ziepe.ca, willy@infradead.org, david@redhat.com,
linux-kernel@vger.kernel.org, nvdimm@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org, jhubbard@nvidia.com, hch@lst.de,
zhang.lyra@gmail.com, debug@rivosinc.com, bjorn@kernel.org,
balbirs@nvidia.com, lorenzo.stoakes@oracle.com,
linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
linux-cxl@vger.kernel.org, dri-devel@lists.freedesktop.org,
John@Groves.net, m.szyprowski@samsung.com
Subject: [PATCH v2 10/14] fs/dax: Remove FS_DAX_LIMITED config option
Date: Mon, 16 Jun 2025 21:58:12 +1000 [thread overview]
Message-ID: <bbade6a3154d14d958f5f9cf65fd6424897ec9c2.1750075065.git-series.apopple@nvidia.com> (raw)
In-Reply-To: <cover.8d04615eb17b9e46fc0ae7402ca54b69e04b1043.1750075065.git-series.apopple@nvidia.com>
The dcssblk driver was the last user of FS_DAX_LIMITED. That was marked
broken by 653d7825c149 ("dcssblk: mark DAX broken, remove FS_DAX_LIMITED
support") to allow removal of PFN_SPECIAL. However the FS_DAX_LIMITED
config option itself was not removed, so do that now.
Signed-off-by: Alistair Popple <apopple@nvidia.com>
---
Changes since v1:
- New for v2.
---
fs/Kconfig | 9 +--------
fs/dax.c | 12 ------------
mm/memremap.c | 4 ----
3 files changed, 1 insertion(+), 24 deletions(-)
diff --git a/fs/Kconfig b/fs/Kconfig
index 44b6cdd..ccdf371 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -59,7 +59,7 @@ endif # BLOCK
config FS_DAX
bool "File system based Direct Access (DAX) support"
depends on MMU
- depends on ZONE_DEVICE || FS_DAX_LIMITED
+ depends on ZONE_DEVICE
select FS_IOMAP
select DAX
help
@@ -95,13 +95,6 @@ config FS_DAX_PMD
depends on ZONE_DEVICE
depends on TRANSPARENT_HUGEPAGE
-# Selected by DAX drivers that do not expect filesystem DAX to support
-# get_user_pages() of DAX mappings. I.e. "limited" indicates no support
-# for fork() of processes with MAP_SHARED mappings or support for
-# direct-I/O to a DAX mapping.
-config FS_DAX_LIMITED
- bool
-
# Posix ACL utility routines
#
# Note: Posix ACLs can be implemented without these helpers. Never use
diff --git a/fs/dax.c b/fs/dax.c
index 7d4ecb9..f4ffb69 100644
--- a/fs/dax.c
+++ b/fs/dax.c
@@ -449,9 +449,6 @@ static void dax_associate_entry(void *entry, struct address_space *mapping,
if (dax_is_zero_entry(entry) || dax_is_empty_entry(entry))
return;
- if (IS_ENABLED(CONFIG_FS_DAX_LIMITED))
- return;
-
index = linear_page_index(vma, address & ~(size - 1));
if (shared && (folio->mapping || dax_folio_is_shared(folio))) {
if (folio->mapping)
@@ -474,9 +471,6 @@ static void dax_disassociate_entry(void *entry, struct address_space *mapping,
{
struct folio *folio = dax_to_folio(entry);
- if (IS_ENABLED(CONFIG_FS_DAX_LIMITED))
- return;
-
if (dax_is_zero_entry(entry) || dax_is_empty_entry(entry))
return;
@@ -768,12 +762,6 @@ struct page *dax_layout_busy_page_range(struct address_space *mapping,
pgoff_t end_idx;
XA_STATE(xas, &mapping->i_pages, start_idx);
- /*
- * In the 'limited' case get_user_pages() for dax is disabled.
- */
- if (IS_ENABLED(CONFIG_FS_DAX_LIMITED))
- return NULL;
-
if (!dax_mapping(mapping))
return NULL;
diff --git a/mm/memremap.c b/mm/memremap.c
index c417c84..c17e0a6 100644
--- a/mm/memremap.c
+++ b/mm/memremap.c
@@ -332,10 +332,6 @@ void *memremap_pages(struct dev_pagemap *pgmap, int nid)
}
break;
case MEMORY_DEVICE_FS_DAX:
- if (IS_ENABLED(CONFIG_FS_DAX_LIMITED)) {
- WARN(1, "File system DAX not supported\n");
- return ERR_PTR(-EINVAL);
- }
params.pgprot = pgprot_decrypted(params.pgprot);
break;
case MEMORY_DEVICE_GENERIC:
--
git-series 0.9.1
next prev parent reply other threads:[~2025-06-16 11:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 11:58 [PATCH v2 00/14] mm: Remove pXX_devmap page table bit and pfn_t type Alistair Popple
2025-06-16 11:58 ` [PATCH v2 01/14] mm: Convert pXd_devmap checks to vma_is_dax Alistair Popple
2025-06-17 9:19 ` David Hildenbrand
2025-06-19 8:40 ` Alistair Popple
2025-06-16 11:58 ` [PATCH v2 02/14] mm: Filter zone device pages returned from folio_walk_start() Alistair Popple
2025-06-17 9:25 ` David Hildenbrand
2025-06-17 9:30 ` David Hildenbrand
2025-06-19 0:41 ` Alistair Popple
2025-06-16 11:58 ` [PATCH v2 03/14] mm: Convert vmf_insert_mixed() from using pte_devmap to pte_special Alistair Popple
2025-06-17 9:49 ` David Hildenbrand
2025-06-18 9:31 ` David Hildenbrand
2025-06-16 11:58 ` [PATCH v2 04/14] mm: Remove remaining uses of PFN_DEV Alistair Popple
2025-06-16 11:58 ` [PATCH v2 05/14] mm/gup: Remove pXX_devmap usage from get_user_pages() Alistair Popple
2025-06-16 11:58 ` [PATCH v2 06/14] mm/huge_memory: Remove pXd_devmap usage from insert_pXd_pfn() Alistair Popple
2025-06-17 9:49 ` David Hildenbrand
2025-06-19 8:52 ` Alistair Popple
2025-06-16 11:58 ` [PATCH v2 07/14] mm: Remove redundant pXd_devmap calls Alistair Popple
2025-06-16 11:58 ` [PATCH v2 08/14] mm/khugepaged: Remove redundant pmd_devmap() check Alistair Popple
2025-06-17 9:44 ` David Hildenbrand
2025-06-19 7:56 ` Alistair Popple
2025-06-16 11:58 ` [PATCH v2 09/14] powerpc: Remove checks for devmap pages and PMDs/PUDs Alistair Popple
2025-06-17 9:37 ` David Hildenbrand
2025-06-16 11:58 ` Alistair Popple [this message]
2025-06-17 9:37 ` [PATCH v2 10/14] fs/dax: Remove FS_DAX_LIMITED config option David Hildenbrand
2025-06-16 11:58 ` [PATCH v2 11/14] mm: Remove devmap related functions and page table bits Alistair Popple
2025-06-17 9:36 ` David Hildenbrand
2025-06-16 11:58 ` [PATCH v2 12/14] mm: Remove PFN_MAP, PFN_SPECIAL, PFN_SG_CHAIN and PFN_SG_LAST Alistair Popple
2025-06-16 11:58 ` [PATCH v2 13/14] mm: Remove callers of pfn_t functionality Alistair Popple
2025-06-17 9:35 ` David Hildenbrand
2025-06-16 11:58 ` [PATCH v2 14/14] mm/memremap: Remove unused devmap_managed_key Alistair Popple
2025-06-17 9:34 ` David Hildenbrand
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=bbade6a3154d14d958f5f9cf65fd6424897ec9c2.1750075065.git-series.apopple@nvidia.com \
--to=apopple@nvidia.com \
--cc=John@Groves.net \
--cc=akpm@linux-foundation.org \
--cc=balbirs@nvidia.com \
--cc=bjorn@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=debug@rivosinc.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=hch@lst.de \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=lorenzo.stoakes@oracle.com \
--cc=m.szyprowski@samsung.com \
--cc=nvdimm@lists.linux.dev \
--cc=willy@infradead.org \
--cc=zhang.lyra@gmail.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).