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
317 key and a single filenames encryption key.  To still encrypt different
710 encrypted, even if it is empty.  Users who want to encrypt an entire
736   kernel config, and the superblock must have had the "encrypt"
737   feature flag enabled using ``tune2fs -O encrypt`` or ``mkfs.ext4 -O
738   encrypt``.)
1324 hardware* that can encrypt/decrypt data while it is on its way to/from
1333 blk-crypto instead of the kernel crypto API to encrypt/decrypt file
1400 Implementation-wise, to encrypt/decrypt the contents of files that are
1498 inline encryption hardware will encrypt/decrypt the file contents.
1500 When inline encryption isn't used, filesystems must encrypt/decrypt
1509 cannot encrypt data in-place in the page cache, since the cached
1510 plaintext must be preserved.  Instead, filesystems must encrypt into a
1561 filesystem test suite.  First, run all the tests in the "encrypt"
1568     kvm-xfstests -c ext4,f2fs -g encrypt
1569     kvm-xfstests -c ext4,f2fs -g encrypt -m inlinecrypt
1575     kvm-xfstests -c ubifs -g encrypt
1583 Besides running the "encrypt" group tests, for ext4 and f2fs it's also
1588 kvm-xfstests, use the "encrypt" filesystem configuration::
1590     kvm-xfstests -c ext4/encrypt,f2fs/encrypt -g auto
1591     kvm-xfstests -c ext4/encrypt,f2fs/encrypt -g auto -m inlinecrypt
1593 Because this runs many more tests than "-g encrypt" does, it takes
1598     gce-xfstests -c ext4/encrypt,f2fs/encrypt -g auto
1599     gce-xfstests -c ext4/encrypt,f2fs/encrypt -g auto -m inlinecrypt