Received-SPF: pass (google.com: domain of linux-kernel+bounces-35137-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Miklos Szeredi <miklos@szeredi.hu>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Vivek Goyal <vgoyal@redhat.com>
Cc: linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Gao Xiang <hsiangkao@linux.alibaba.com>
Subject: [PATCH] virtiofs: avoid unnecessary VM_MIXEDMAP for mmap support
Date: Tue, 23 Jan 2024 18:58:03 +0800
Message-Id: <20240123105803.1725795-1-hsiangkao@linux.alibaba.com>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

After commit e1fb4a0864958 ("dax: remove VM_MIXEDMAP for fsdax and
device dax"), VM_MIXEDMAP seems unnecessary for virtiofs DAX mapping
(devmap).

At least I'm not sure why VM_MIXEDMAP is used during some internal
review (I guess that was added due to the current DAX documentation),
it could avoid copying page table when forking since page faults could
fill DAX VMAs just fine.

Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
---
 fs/fuse/dax.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/fuse/dax.c b/fs/fuse/dax.c
index 12ef91d170bb..5a3c17a80340 100644
--- a/fs/fuse/dax.c
+++ b/fs/fuse/dax.c
@@ -858,7 +858,7 @@ int fuse_dax_mmap(struct file *file, struct vm_area_struct *vma)
 {
 	file_accessed(file);
 	vma->vm_ops = &fuse_dax_vm_ops;
-	vm_flags_set(vma, VM_MIXEDMAP | VM_HUGEPAGE);
+	vm_flags_set(vma, VM_HUGEPAGE);
 	return 0;
 }
 
-- 
2.39.3