Lines Matching full:encrypted

165 	 * filesystem may write encrypted file contents, NULL if the filesystem
173 	 * devices that aren't used for encrypted file contents, such as
197  * Return: %true iff the inode is an encrypted regular file and the kernel was
225  * dentry that was created in an encrypted directory that hasn't had its
228  * When a filesystem is asked to create a new filename in an encrypted directory
833  * @inode: an inode. If encrypted, its key must be set up.
848  * @inode: an inode. If encrypted, its key must be set up.
875  * fscrypt_prepare_link() - prepare to link an inode into a possibly-encrypted
881  * A new link can only be added to an encrypted directory if the directory's
886  * in an encrypted directory tree use the same encryption policy.
902  * fscrypt_prepare_rename() - prepare for a rename between possibly-encrypted
911  * encrypted.  A new link can only be added to an encrypted directory if the
918  * in an encrypted directory tree use the same encryption policy.
936  * fscrypt_prepare_lookup() - prepare to lookup a name in a possibly-encrypted
942  * Prepare for ->lookup() in a directory which may be encrypted by determining
973  * fscrypt_prepare_readdir() - prepare to read a possibly-encrypted directory
976  * If the directory is encrypted and it doesn't already have its encryption key
993  * fscrypt_prepare_setattr() - prepare to change a possibly-encrypted inode's
998  * Prepare for ->setattr() on a possibly-encrypted inode.  On an encrypted file,
1025  * If the symlink target needs to be encrypted, then this function encrypts it