Query: debugfs_create_u32_array
OS: centos
Section: 9
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
DEBUGFS_CREATE_U32_A(9) The debugfs filesystem DEBUGFS_CREATE_U32_A(9)NAMEdebugfs_create_u32_array - create a debugfs file that is used to read u32 array.SYNOPSISstruct dentry * debugfs_create_u32_array(const char * name, umode_t mode, struct dentry * parent, u32 * array, u32 elements);ARGUMENTSname 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. array u32 array that provides data. elements total number of elements in the array.DESCRIPTIONThis function creates a file in debugfs with the given name that exports array as data. If the mode variable is so set it can be read from. Writing is not supported. Seek within the file is also not supported. Once array is created its size can not be changed. The function returns a pointer to dentry on success. If debugfs is not enabled in the kernel, the value -ENODEV will be returned.COPYRIGHTKernel Hackers Manual 3.10 June 2014 DEBUGFS_CREATE_U32_A(9)
Related Man Pages |
---|
debugfs_create_regset32(9) - centos |
debugfs_create_file(9) - centos |
debugfs_create_u16(9) - suse |
debugfs_create_u64(9) - suse |
debugfs_create_u8(9) - suse |
Similar Topics in the Unix Linux Community |
---|
Weird 'find' results |
How to increment version inside a file? |
CentOS7 restoring file capabilities |
Unsure why access time on a directory change isn't changing |
Controlling user input |