fscrypt: make fscrypt_set_test_dummy_encryption() take a 'const char *'
authorEric Biggers <ebiggers@google.com>
Thu, 17 Sep 2020 04:11:36 +0000 (21:11 -0700)
committerEric Biggers <ebiggers@google.com>
Tue, 22 Sep 2020 13:48:52 +0000 (06:48 -0700)
commitc8c868abc91ff23f6f5c4444c419de7c277d77e1
tree93dd9591ebdf07595aec0c346ea222e91280d4ba
parentac4acb1f4b2b6b7e8d913537cccec8789903e164
fscrypt: make fscrypt_set_test_dummy_encryption() take a 'const char *'

fscrypt_set_test_dummy_encryption() requires that the optional argument
to the test_dummy_encryption mount option be specified as a substring_t.
That doesn't work well with filesystems that use the new mount API,
since the new way of parsing mount options doesn't use substring_t.

Make it take the argument as a 'const char *' instead.

Instead of moving the match_strdup() into the callers in ext4 and f2fs,
make them just use arg->from directly.  Since the pattern is
"test_dummy_encryption=%s", the argument will be null-terminated.

Acked-by: Jeff Layton <jlayton@kernel.org>
Link: https://lore.kernel.org/r/20200917041136.178600-14-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@google.com>
fs/crypto/policy.c
fs/ext4/super.c
fs/f2fs/super.c
include/linux/fscrypt.h