Lines Matching full:encrypt
26 at the block device level. This allows it to encrypt different files
30 However, except for filenames, fscrypt does not encrypt filesystem
290 key and a single filenames encryption key. To still encrypt different
540 encrypted, even if it is empty. Users who want to encrypt an entire
566 kernel config, and the superblock must have had the "encrypt"
567 feature flag enabled using ``tune2fs -O encrypt`` or ``mkfs.ext4 -O
568 encrypt``.)
1198 cannot encrypt data in-place in the page cache, since the cached
1199 plaintext must be preserved. Instead, filesystems must encrypt into a
1262 filesystem test suite. First, run all the tests in the "encrypt"
1269 kvm-xfstests -c ext4,f2fs -g encrypt
1270 kvm-xfstests -c ext4,f2fs -g encrypt -m inlinecrypt
1276 kvm-xfstests -c ubifs -g encrypt
1284 Besides running the "encrypt" group tests, for ext4 and f2fs it's also
1289 kvm-xfstests, use the "encrypt" filesystem configuration::
1291 kvm-xfstests -c ext4/encrypt,f2fs/encrypt -g auto
1292 kvm-xfstests -c ext4/encrypt,f2fs/encrypt -g auto -m inlinecrypt
1294 Because this runs many more tests than "-g encrypt" does, it takes
1299 gce-xfstests -c ext4/encrypt,f2fs/encrypt -g auto
1300 gce-xfstests -c ext4/encrypt,f2fs/encrypt -g auto -m inlinecrypt