securityfs_create_dentry
Prev | Chapter 11. Security Framework | Next

## Name

securityfs_create_dentry — create a file/dir in the securityfs filesystem

## Synopsis

`struct dentry * securityfs_create_dentry (` | const char * name,
| umode_t mode,
| struct dentry * parent,
| void * data,
| const struct file_operations * fops,
| const struct inode_operations * iops`)`;

## 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.

`iops`

  a point to a struct of inode_operations that should be used for this file/dir

## Description

This is the basic “create a xxx” 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 error value (via ERR_PTR).

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

Prev | Up | Next
security_module_enable | Home | securityfs_create_file