DEBUGFS_CREATE_U8(9) The debugfs filesystem DEBUGFS_CREATE_U8(9)NAME
debugfs_create_u8 - create a debugfs file that is used to read and write an unsigned 8-bit value
SYNOPSIS
struct dentry * debugfs_create_u8(const char * name, umode_t mode, struct dentry * parent, u8 * 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_U8(9)
Check Out this Related Man Page
DEBUGFS_CREATE_BOOL(9) The debugfs filesystem DEBUGFS_CREATE_BOOL(9)NAME
debugfs_create_bool - create a debugfs file that is used to read and write a boolean value
SYNOPSIS
struct dentry * debugfs_create_bool(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_BOOL(9)
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)
Being a novice user to linux i m little unaware of how would i check disk read write speed.
One of my mate is suggesting to create a file using dd command and check how much time it takes to create a 30 gb file .
I think this has a little sense however i would also like to take your reviews... (5 Replies)