include/linux/fscrypt.h

3  * fscrypt.h: declarations for per-file encryption
5  * Filesystems that implement per-file encryption must include this header
23  * This is needed to ensure that all contents encryption modes will work, as
29  * compression), then it will need to pad to this alignment before encryption.
67 	 * first time an encryption key is set up for a file.  The bounce page
78 	 * If set, then fs/crypto/ will allow the use of encryption settings
82 	 * if the filesystem wants to support inline encryption hardware that is
165 	 * encryption without the possibility of files becoming unreadable.
188 	 * external journal devices), and wants to support inline encryption,
211  *					 contents encryption
227  * plaintext alias as a result of the encryption key being added,
257  * encryption key added yet.  Such dentries may be either positive or negative.
266  * encryption key, but just checking for the key on the directory inode during
701 	/* Encryption support disabled; use standard comparison */  in fscrypt_match_name()
897  *					encryption
900  * Return: true if the inode requires file contents encryption and if the
901  *	   encryption should be done in the block layer via blk-crypto rather
912  *					  encryption
915  * Return: true if the inode requires file contents encryption and if the
916  *	   encryption should be done in the filesystem layer rather than in the
929  * Return: %true if the inode has had its encryption key set up, else %false.
947  * encryption key is available --- since otherwise we'd have no way to encrypt
951  * in an encrypted directory tree use the same encryption policy.
953  * Return: 0 on success, -ENOKEY if the directory's encryption key is missing,
954  * -EXDEV if the link would result in an inconsistent encryption policy, or
977  * directory's encryption key is available --- since otherwise we'd have no way
983  * in an encrypted directory tree use the same encryption policy.
985  * Return: 0 on success, -ENOKEY if an encryption key is missing, -EXDEV if the
986  * rename would cause inconsistent encryption policies, or another -errno code.
1009  * directory's encryption policy is supported by this kernel and its encryption
1017  * directory's encryption key is later added.
1044  * If the directory is encrypted and it doesn't already have its encryption key
1048  * Return: 0 on success; -errno on error.  Note that the encryption key being
1050  *	   the encryption policy is unsupported by this kernel; that is treated
1067  * most attribute changes are allowed even without the encryption key.  However,
1068  * without the encryption key we do have to forbid truncates.  This is needed
1076  * if a problem occurred while setting up the encryption key.