d_add_ci(9) [suse man page]

D_ADD_CI(9)							   The Linux VFS						       D_ADD_CI(9)

NAME

       d_add_ci - lookup or allocate new dentry with case-exact name

SYNOPSIS

       struct dentry * d_add_ci(struct dentry * dentry, struct inode * inode, struct qstr * name);

ARGUMENTS

       dentry
	   the negative dentry that was passed to the parent's lookup func

       inode
	   the inode case-insensitive lookup has found

       name
	   the case-exact name to be associated with the returned dentry

DESCRIPTION

       This is to avoid filling the dcache with case-insensitive names to the same inode, only the actual correct case is stored in the dcache for
       case-insensitive filesystems.

       For a case-insensitive lookup match and if the the case-exact dentry already exists in in the dcache, use it and return it.

       If no entry exists with the exact case name, allocate new dentry with the exact case, and return the spliced entry.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010							       D_ADD_CI(9)

SECURITYFS_CREATE_FI(9) 					Security Framework					   SECURITYFS_CREATE_FI(9)

NAME

       securityfs_create_file - create a file in the securityfs filesystem

SYNOPSIS

       struct dentry * securityfs_create_file(const char * name, umode_t mode, struct dentry * parent, void * data,
					      const struct file_operations * fops);

ARGUMENTS

       name
	   a pointer to a string containing the name of the file to create.

       mode
	   the permission that the file should have

       parent
	   a pointer to the parent dentry for this file. This should be a directory dentry if set. If this parameter is NULL, then the file will
	   be created in the root of the securityfs filesystem.

       data
	   a pointer to something that the caller will want to get to later on. The inode.i_private pointer will point to this value on the open
	   call.

       fops
	   a pointer to a struct file_operations that should be used for this file.

DESCRIPTION

       This is the basic "create a file" function for securityfs. It allows for a wide range of flexibility in creating a file, or a directory (if
       you want to create a directory, the securityfs_create_dir function is recommended to be used instead).

       This function returns a pointer to a dentry if it succeeds. This pointer must be passed to the securityfs_remove function when the file is
       to be removed (no automatic cleanup happens if your module is unloaded, you are responsible here). If an error occurs, the function will
       return the erorr value (via ERR_PTR).

       If securityfs is not enabled in the kernel, the value -ENODEV is returned.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   SECURITYFS_CREATE_FI(9)