From: Eric Biggers <ebigg...@google.com>

Now that fs/crypto/ adds the test dummy encryption key on-demand when
it's needed, there's no need for individual filesystems to call
fscrypt_add_test_dummy_key().  Remove the call to it from f2fs.

Signed-off-by: Eric Biggers <ebigg...@google.com>
---
 fs/f2fs/super.c | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 1f812b9ce985b..64d3556d61a55 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -540,12 +540,6 @@ static int f2fs_set_test_dummy_encryption(struct 
super_block *sb,
                                  opt, err);
                return -EINVAL;
        }
-       err = fscrypt_add_test_dummy_key(sb, policy);
-       if (err) {
-               f2fs_warn(sbi, "Error adding test dummy encryption key [%d]",
-                         err);
-               return err;
-       }
        f2fs_warn(sbi, "Test dummy encryption mode enabled");
        return 0;
 }
-- 
2.39.1



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Reply via email to