Lines Matching full:encryption

3  * fscrypt.h: declarations for per-file encryption
5  * Filesystems that implement per-file encryption must include this header
128 	 * encryption without the possibility of files becoming unreadable.
161 	 * external journal devices), and wants to support inline encryption,
189  *					 contents encryption
205  * as a result of the encryption key being added, DCACHE_NOKEY_NAME must be
221  * encryption key added yet.  Such dentries may be either positive or negative.
230  * encryption key, but just checking for the key on the directory inode during
578 	/* Encryption support disabled; use standard comparison */  in fscrypt_match_name()
752  *					encryption
755  * Return: true if the inode requires file contents encryption and if the
756  *	   encryption should be done in the block layer via blk-crypto rather
767  *					  encryption
770  * Return: true if the inode requires file contents encryption and if the
771  *	   encryption should be done in the filesystem layer rather than in the
784  * Return: %true if the inode has had its encryption key set up, else %false.
802  * encryption key is available --- since otherwise we'd have no way to encrypt
806  * in an encrypted directory tree use the same encryption policy.
808  * Return: 0 on success, -ENOKEY if the directory's encryption key is missing,
809  * -EXDEV if the link would result in an inconsistent encryption policy, or
832  * directory's encryption key is available --- since otherwise we'd have no way
838  * in an encrypted directory tree use the same encryption policy.
840  * Return: 0 on success, -ENOKEY if an encryption key is missing, -EXDEV if the
841  * rename would cause inconsistent encryption policies, or another -errno code.
864  * directory's encryption policy is supported by this kernel and its encryption
872  * directory's encryption key is later added.
896  * If the directory is encrypted and it doesn't already have its encryption key
900  * Return: 0 on success; -errno on error.  Note that the encryption key being
902  *	   the encryption policy is unsupported by this kernel; that is treated
919  * most attribute changes are allowed even without the encryption key.  However,
920  * without the encryption key we do have to forbid truncates.  This is needed
928  * if a problem occurred while setting up the encryption key.