Lines Matching full:encrypted

179 	 * filesystem may write encrypted file contents, NULL if the filesystem
187 	 * devices that aren't used for encrypted file contents, such as
215  * Return: %true iff the inode is an encrypted regular file and the kernel was
257  * dentry that was created in an encrypted directory that hasn't had its
260  * When a filesystem is asked to create a new filename in an encrypted directory
299 		 * Unencrypted dentries and encrypted dentries where the  in fscrypt_prepare_dentry()
899  * @inode: an inode. If encrypted, its key must be set up.
914  * @inode: an inode. If encrypted, its key must be set up.
941  * fscrypt_prepare_link() - prepare to link an inode into a possibly-encrypted
947  * A new link can only be added to an encrypted directory if the directory's
952  * in an encrypted directory tree use the same encryption policy.
968  * fscrypt_prepare_rename() - prepare for a rename between possibly-encrypted
977  * encrypted.  A new link can only be added to an encrypted directory if the
984  * in an encrypted directory tree use the same encryption policy.
1002  * fscrypt_prepare_lookup() - prepare to lookup a name in a possibly-encrypted
1008  * Prepare for ->lookup() in a directory which may be encrypted by determining
1042  * fscrypt_prepare_readdir() - prepare to read a possibly-encrypted directory
1045  * If the directory is encrypted and it doesn't already have its encryption key
1062  * fscrypt_prepare_setattr() - prepare to change a possibly-encrypted inode's
1067  * Prepare for ->setattr() on a possibly-encrypted inode.  On an encrypted file,
1094  * If the symlink target needs to be encrypted, then this function encrypts it