Lines Matching full:encryption

5  * Encryption hooks for higher-level filesystem operations.
15  * Currently, an encrypted regular file can only be opened if its encryption key
17  * Therefore, we first set up the inode's encryption key (if not already done)
22  * encryption policy.  This is needed as part of the enforcement that all files
23  * in an encrypted directory tree use the same encryption policy, as a
44 	 * encryption policy comparison, but it's expensive on multi-core  in fscrypt_file_open()
63 			     "Inconsistent encryption context (parent directory: %lu)",  in fscrypt_file_open()
137  * filesystems that handle filename encryption and no-key name encoding
139  * fscrypt_prepare_lookup(), this will try to set up the directory's encryption
143  * Return: 0 on success; -errno on error.  Note that the encryption key being
145  *	   the encryption policy is unsupported by this kernel; that is treated
194 	 * if the directory uses a v2 encryption policy.  in fscrypt_prepare_setflags()
235  * -ENOKEY if the encryption key is missing, or another -errno code if a problem
236  * occurred while setting up the encryption key.
247 	 * the encryption policy which will be inherited from the directory.  in fscrypt_prepare_symlink()
293 	 * symlink inode's encryption key.  We don't wait until now to do it,  in __fscrypt_encrypt_symlink()
346  * If the symlink's encryption key is available, we decrypt its target.
372 	 * Try to set up the symlink's encryption key, but we can continue  in fscrypt_get_symlink()
441  * inode's encryption key if possible, and then decrypting or encoding the