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
691 encrypted, even if it is empty.  Users who want to encrypt an entire
717   kernel config, and the superblock must have had the "encrypt"
718   feature flag enabled using ``tune2fs -O encrypt`` or ``mkfs.ext4 -O
719   encrypt``.)
1302 encryption hardware* that can encrypt/decrypt data while it is on its
1311 blk-crypto instead of the kernel crypto API to encrypt/decrypt file
1406 inline encryption hardware will encrypt/decrypt the file contents.
1408 When inline encryption isn't used, filesystems must encrypt/decrypt
1417 cannot encrypt data in-place in the page cache, since the cached
1418 plaintext must be preserved.  Instead, filesystems must encrypt into a
1469 filesystem test suite.  First, run all the tests in the "encrypt"
1476     kvm-xfstests -c ext4,f2fs -g encrypt
1477     kvm-xfstests -c ext4,f2fs -g encrypt -m inlinecrypt
1483     kvm-xfstests -c ubifs -g encrypt
1491 Besides running the "encrypt" group tests, for ext4 and f2fs it's also
1496 kvm-xfstests, use the "encrypt" filesystem configuration::
1498     kvm-xfstests -c ext4/encrypt,f2fs/encrypt -g auto
1499     kvm-xfstests -c ext4/encrypt,f2fs/encrypt -g auto -m inlinecrypt
1501 Because this runs many more tests than "-g encrypt" does, it takes
1506     gce-xfstests -c ext4/encrypt,f2fs/encrypt -g auto
1507     gce-xfstests -c ext4/encrypt,f2fs/encrypt -g auto -m inlinecrypt