Lines Matching full:encryption

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
120  * encryption key added yet.  Such dentries may be either positive or negative.
129  * encryption key, but just checking for the key on the directory inode during
480 	/* Encryption support disabled; use standard comparison */  in fscrypt_match_name()
643  *					encryption
646  * Return: true if the inode requires file contents encryption and if the
647  *	   encryption should be done in the block layer via blk-crypto rather
658  *					  encryption
661  * Return: true if the inode requires file contents encryption and if the
662  *	   encryption should be done in the filesystem layer rather than in the
675  * Return: %true if the inode has had its encryption key set up, else %false.
686  * fscrypt_require_key() - require an inode's encryption key
689  * If the inode is encrypted, set up its encryption key if not already done.
696  * if a problem occurred while setting up the encryption key.
719  * encryption key is available --- since otherwise we'd have no way to encrypt
720  * the filename.  Therefore, we first set up the directory's encryption key (if
724  * in an encrypted directory tree use the same encryption policy.
726  * Return: 0 on success, -ENOKEY if the directory's encryption key is missing,
727  * -EXDEV if the link would result in an inconsistent encryption policy, or
750  * directory's encryption key is available --- since otherwise we'd have no way
756  * in an encrypted directory tree use the same encryption policy.
758  * Return: 0 on success, -ENOKEY if an encryption key is missing, -EXDEV if the
759  * rename would cause inconsistent encryption policies, or another -errno code.
782  * directory's encryption key is available, then the lookup is assumed to be by
813  * most attribute changes are allowed even without the encryption key.  However,
814  * without the encryption key we do have to forbid truncates.  This is needed
822  * if a problem occurred while setting up the encryption key.