d_instantiate(9) [centos man page]

D_INSTANTIATE(9)						   The Linux VFS						  D_INSTANTIATE(9)

NAME

       d_instantiate - fill in inode information for a dentry

SYNOPSIS

       void d_instantiate(struct dentry * entry, struct inode * inode);

ARGUMENTS

       entry
	   dentry to complete

       inode
	   inode to attach to this dentry

DESCRIPTION

       Fill in inode information in the entry.

       This turns negative dentries into productive full members of society.

       NOTE! This assumes that the inode count has been incremented (or otherwise set) by the caller to indicate that it is now in use by the
       dcache.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							  D_INSTANTIATE(9)

DEBUGFS_CREATE_FILE(9)					      The debugfs filesystem					    DEBUGFS_CREATE_FILE(9)

NAME

       debugfs_create_file - create a file in the debugfs filesystem

SYNOPSIS

       struct dentry * debugfs_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 paramater is NULL, then the file will
	   be created in the root of the debugfs 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 debugfs. It allows for a wide range of flexibility in creating a file, or a directory (if
       you want to create a directory, the debugfs_create_dir function is recommended to be used instead.)

       This function will return a pointer to a dentry if it succeeds. This pointer must be passed to the debugfs_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, NULL will be
       returned.

       If debugfs is not enabled in the kernel, the value -ENODEV will be returned.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						    DEBUGFS_CREATE_FILE(9)