Documentation/filesystems/fscrypt.rst

242 files doesn't map to the same ciphertext, or vice versa.  In most
252 filesystem's inode table, and there didn't appear to be any
386 Generally speaking, these ciphers aren't "bad" per se, but they
388 AES and ChaCha.  They also don't bring much new to the table.  It is
407 the file contents mode doesn't need to supported in the kernel crypto
895 have to be used.  Second, it doesn't match the fact that the
940 These ioctls don't work on keys that were added via the legacy
993 try to "lock" all files that had been unlocked with the key.  It won't
1140   may be used to overwrite the source files but isn't guaranteed to be
1240 model isn't particularly efficient and fscrypt hasn't been optimized
1259 encryption when possible; it doesn't force its use.  fscrypt will
1261 inline encryption hardware doesn't have the needed crypto capabilities
1271 Inline encryption doesn't affect the ciphertext or other aspects of
1349 When inline encryption isn't used, filesystems must encrypt/decrypt