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)
Check Out this Related Man Page
DEBUGFS_CREATE_U32(9) The debugfs filesystem DEBUGFS_CREATE_U32(9)NAME
debugfs_create_u32 - create a debugfs file that is used to read and write an unsigned 32-bit value
SYNOPSIS
struct dentry * debugfs_create_u32(const char * name, umode_t mode, struct dentry * parent, u32 * value);
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 debugfs filesystem.
value
a pointer to the variable that the file should read to and write from.
DESCRIPTION
This function creates a file in debugfs with the given name that contains the value of the variable value. If the mode variable is so set,
it can be read from, and written to.
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. It is not wise to check for this value, but rather, check for
NULL or !NULL instead as to eliminate the need for #ifdef in the calling code.
COPYRIGHT Kernel Hackers Manual 3.10 June 2014 DEBUGFS_CREATE_U32(9)
I have just installed 5.0.7 of openserver and forgot to create a /u filesystem.
I have a root filesystem that takes up most of the hard disc space and I want to reduce the size of that and create a /u.
I have tried divvy amd mkdev fs but to no avail.
Could somebody give me some idea as to how I... (2 Replies)
using debugfs we can restore the deleted file provided if we know the inode no. of the same file
can anyone tell me how to use this command in practically.Below the inode of a file caled minfo.txt.I m using IBM AIX 5.3
90139 minfo.txt
-------------------------------- (3 Replies)
I have a basic knowledge of the various structures like file, dentry, inode, superblocks of linux virtual file systems.
I want to get a more deep insight as to how these structures are utilized in reality. I mean I want to get an understanding of how and where these structure come up in picture... (4 Replies)
what are the functions of all these files
dentry.c
inode.c
file.c
inode.c
lookup.c
main.c
mmap.c
or could anyone provide any link explaining all the functions and tasks performed by these files. :confused::confused:(:(
edit by bakunin: Please give your threads meaningful titles.... (1 Reply)