From: Eric Biggers <ebiggers@xxxxxxxxxx> We were relying on the kernel setting the 'encrypt' feature flag for us. We should just do it in userspace when formatting the filesystem. This will allow us to eventually remove the kernel-side hack to force-set the 'encrypt' flag in the superblock. Signed-off-by: Eric Biggers <ebiggers@xxxxxxxxxx> --- kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt index 390e205..320eff0 100644 --- a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt +++ b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt @@ -1,5 +1,5 @@ SIZE=small -export MKFS_OPTIONS="" +export MKFS_OPTIONS="-O encrypt" export EXT_MOUNT_OPTIONS="test_dummy_encryption" REQUIRE_FEATURE=encryption TESTNAME="Ext4 encryption" -- 2.11.0.483.g087da7b7c-goog -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
