cifs: wire up >migrate_folio

CIFS does not use page private data that needs migration, so it can just
wire up filemap_migrate_folio.  This prepares for removing ->writepage,
which is used as a fallback if no migrate_folio method is set.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
Signed-off-by: Steve French <stfrench@microsoft.com>

diff --git a/fs/cifs/file.c b/fs/cifs/file.c
index cd96982..6be924c 100644 (file)
--- a/fs/cifs/file.c
+++ b/fs/cifs/file.c
@@ -5240,10 +5240,10 @@ const struct address_space_operations cifs_addr_ops = {
        .direct_IO = cifs_direct_io,
        .invalidate_folio = cifs_invalidate_folio,
        .launder_folio = cifs_launder_folio,
+       .migrate_folio = filemap_migrate_folio,
        /*
-        * TODO: investigate and if useful we could add an cifs_migratePage
-        * helper (under an CONFIG_MIGRATION) in the future, and also
-        * investigate and add an is_dirty_writeback helper if needed
+        * TODO: investigate and if useful we could add an is_dirty_writeback
+        * helper if needed
         */
        .swap_activate = cifs_swap_activate,
        .swap_deactivate = cifs_swap_deactivate,
@@ -5264,4 +5264,5 @@ const struct address_space_operations cifs_addr_ops_smallbuf = {
        .release_folio = cifs_release_folio,
        .invalidate_folio = cifs_invalidate_folio,
        .launder_folio = cifs_launder_folio,
+       .migrate_folio = filemap_migrate_folio,
 };