[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <176169812293.1426649.14459335530115245604.stgit@frogsfrogsfrogs>
Date: Tue, 28 Oct 2025 17:58:47 -0700
From: "Darrick J. Wong" <djwong@...nel.org>
To: djwong@...nel.org, miklos@...redi.hu
Cc: joannelkoong@...il.com, bernd@...ernd.com, neal@...pa.dev,
 linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: [PATCH 10/10] fuse: enable iomap
From: Darrick J. Wong <djwong@...nel.org>
Remove the guard that we used to avoid bisection problems.
Signed-off-by: "Darrick J. Wong" <djwong@...nel.org>
---
 fs/fuse/file_iomap.c |    3 ---
 1 file changed, 3 deletions(-)
diff --git a/fs/fuse/file_iomap.c b/fs/fuse/file_iomap.c
index 94a9c51f3d75e5..9d77f4db32d7fd 100644
--- a/fs/fuse/file_iomap.c
+++ b/fs/fuse/file_iomap.c
@@ -105,9 +105,6 @@ void fuse_iomap_sysfs_cleanup(struct kobject *fuse_kobj)
 
 bool fuse_iomap_enabled(void)
 {
-	/* Don't let anyone touch iomap until the end of the patchset. */
-	return false;
-
 	/*
 	 * There are fears that a fuse+iomap server could somehow DoS the
 	 * system by doing things like going out to lunch during a writeback
Powered by blists - more mailing lists
 
