register_security(9) [centos man page]

REGISTER_SECURITY(9)						Security Framework					      REGISTER_SECURITY(9)

NAME

       register_security - registers a security framework with the kernel

SYNOPSIS

       int register_security(struct security_operations * ops);

ARGUMENTS

       ops
	   a pointer to the struct security_options that is to be registered

DESCRIPTION

       This function allows a security module to register itself with the kernel security subsystem. Some rudimentary checking is done on the ops
       value passed to this function. You'll need to check first if your LSM is allowed to register its ops by calling
       security_module_enable(ops).

       If there is already a security module registered with the kernel, an error will be returned. Otherwise 0 is returned on success.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						      REGISTER_SECURITY(9)

DEBUGFS_CREATE_REGSE(9) 				      The debugfs filesystem					   DEBUGFS_CREATE_REGSE(9)

NAME

       debugfs_create_regset32 - create a debugfs file that returns register values

SYNOPSIS

       struct dentry * debugfs_create_regset32(const char * name, umode_t mode, struct dentry * parent, struct debugfs_regset32 * regset);

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.

       regset
	   a pointer to a struct debugfs_regset32, which contains a pointer to an array of register definitions, the array size and the base
	   address where the register bank is to be found.

DESCRIPTION

       This function creates a file in debugfs with the given name that reports the names and values of a set of 32-bit registers. If the mode
       variable is so set it can be read from. Writing is not supported.

       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_REGSE(9)