include/linux/fscrypt.h

3  * fscrypt.h: declarations for per-file encryption
5  * Filesystems that implement per-file encryption must include this header
95  *					 contents encryption
111  * as a result of the encryption key being added, DCACHE_NOKEY_NAME must be
127  * encryption key added yet.  Such dentries may be either positive or negative.
136  * encryption key, but just checking for the key on the directory inode during
484 	/* Encryption support disabled; use standard comparison */  in fscrypt_match_name()
690  *					encryption
693  * Return: true if the inode requires file contents encryption and if the
694  *	   encryption should be done in the block layer via blk-crypto rather
705  *					  encryption
708  * Return: true if the inode requires file contents encryption and if the
709  *	   encryption should be done in the filesystem layer rather than in the
722  * Return: %true if the inode has had its encryption key set up, else %false.
740  * encryption key is available --- since otherwise we'd have no way to encrypt
744  * in an encrypted directory tree use the same encryption policy.
746  * Return: 0 on success, -ENOKEY if the directory's encryption key is missing,
747  * -EXDEV if the link would result in an inconsistent encryption policy, or
770  * directory's encryption key is available --- since otherwise we'd have no way
776  * in an encrypted directory tree use the same encryption policy.
778  * Return: 0 on success, -ENOKEY if an encryption key is missing, -EXDEV if the
779  * rename would cause inconsistent encryption policies, or another -errno code.
802  * directory's encryption policy is supported by this kernel and its encryption
810  * directory's encryption key is later added.
834  * If the directory is encrypted and it doesn't already have its encryption key
838  * Return: 0 on success; -errno on error.  Note that the encryption key being
840  *	   the encryption policy is unsupported by this kernel; that is treated
857  * most attribute changes are allowed even without the encryption key.  However,
858  * without the encryption key we do have to forbid truncates.  This is needed
866  * if a problem occurred while setting up the encryption key.