include/linux/fscrypt.h

3  * fscrypt.h: declarations for per-file encryption
5  * Filesystems that implement per-file encryption must include this header
88  *					 contents encryption
104  * as a result of the encryption key being added, DCACHE_NOKEY_NAME must be
445 	/* Encryption support disabled; use standard comparison */  in fscrypt_match_name()
602  *					encryption
605  * Return: true if the inode requires file contents encryption and if the
606  *	   encryption should be done in the block layer via blk-crypto rather
617  *					  encryption
620  * Return: true if the inode requires file contents encryption and if the
621  *	   encryption should be done in the filesystem layer rather than in the
634  * Return: %true if the inode has had its encryption key set up, else %false.
645  * fscrypt_require_key() - require an inode's encryption key
648  * If the inode is encrypted, set up its encryption key if not already done.
655  * if a problem occurred while setting up the encryption key.
678  * encryption key is available --- since otherwise we'd have no way to encrypt
679  * the filename.  Therefore, we first set up the directory's encryption key (if
683  * in an encrypted directory tree use the same encryption policy.
685  * Return: 0 on success, -ENOKEY if the directory's encryption key is missing,
686  * -EXDEV if the link would result in an inconsistent encryption policy, or
709  * directory's encryption key is available --- since otherwise we'd have no way
715  * in an encrypted directory tree use the same encryption policy.
717  * Return: 0 on success, -ENOKEY if an encryption key is missing, -EXDEV if the
718  * rename would cause inconsistent encryption policies, or another -errno code.
741  * directory's encryption key is available, then the lookup is assumed to be by
772  * most attribute changes are allowed even without the encryption key.  However,
773  * without the encryption key we do have to forbid truncates.  This is needed
781  * if a problem occurred while setting up the encryption key.