summaryrefslogtreecommitdiff
path: root/fs/smb/client/fscache.c
diff options
context:
space:
mode:
authorDavid Howells <dhowells@redhat.com>2023-10-06 20:29:59 +0300
committerDavid Howells <dhowells@redhat.com>2024-05-01 20:08:21 +0300
commit3ee1a1fc39819906f04d6c62c180e760cd3a689d (patch)
tree600906ca1cb97992663a0586456ce73434571653 /fs/smb/client/fscache.c
parent69c3c023af25edb5433a2db824d3e7cc328f0183 (diff)
downloadlinux-3ee1a1fc39819906f04d6c62c180e760cd3a689d.tar.xz
cifs: Cut over to using netfslib
Make the cifs filesystem use netfslib to handle reading and writing on behalf of cifs. The changes include: (1) Various read_iter/write_iter type functions are turned into wrappers around netfslib API functions or are pointed directly at those functions: cifs_file_direct{,_nobrl}_ops switch to use netfs_unbuffered_read_iter and netfs_unbuffered_write_iter. Large pieces of code that will be removed are #if'd out and will be removed in subsequent patches. [?] Why does cifs mark the page dirty in the destination buffer of a DIO read? Should that happen automatically? Does netfs need to do that? Signed-off-by: David Howells <dhowells@redhat.com> cc: Steve French <sfrench@samba.org> cc: Shyam Prasad N <nspmangalore@gmail.com> cc: Rohith Surabattula <rohiths.msft@gmail.com> cc: Jeff Layton <jlayton@kernel.org> cc: linux-cifs@vger.kernel.org cc: netfs@lists.linux.dev cc: linux-fsdevel@vger.kernel.org cc: linux-mm@kvack.org
Diffstat (limited to 'fs/smb/client/fscache.c')
-rw-r--r--fs/smb/client/fscache.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/fs/smb/client/fscache.c b/fs/smb/client/fscache.c
index 1a895e6243ee..b36c493f4c56 100644
--- a/fs/smb/client/fscache.c
+++ b/fs/smb/client/fscache.c
@@ -171,6 +171,7 @@ void cifs_fscache_release_inode_cookie(struct inode *inode)
}
}
+#if 0 // TODO remove
/*
* Fallback page reading interface.
*/
@@ -279,3 +280,4 @@ int __cifs_fscache_query_occupancy(struct inode *inode,
fscache_end_operation(&cres);
return ret;
}
+#endif