NAME<\/a> init_module, cleanup_module \u2212 module load and unload functions<\/p>\n #include int init_module(void); These functions are not part of the kernel but entry points into loadable modules. These are the only symbols that must be externally defined in order to load a module into a running kernel.<\/p>\n When a module is loaded into a running kernel, the init_module<\/b>(9) function within that object file is called to set up the module. The implementation of that function initializes local features and uses functions such as register_chrdev<\/b>(9) to attach itself to the kernel. It then returns zero(0) if it succeeds. If there is a problem or the module decides that it cannot be loaded, it returns instead an error code (i.e. -ENODEV<\/i>) and the kernel releases the module again.<\/p>\n Once loaded, the cleanup_module<\/b>(9) function of a module is used by the kernel to remove the module again. The module detaches itself from the kernel and returns.<\/p>\n The init_module<\/b>(9) function returns 0 on success, or an error code <0 if the module cannot be initialized.<\/p>\n Linux 1.0+<\/p>\n MOD_INC_USE_COUNT<\/b>(9), insmod<\/b>(1)<\/p>\n Also list some source files for the kernel that implement the functions of the page.<\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
RETURN VALUE<\/a>
AVAILABILITY<\/a>
SEE ALSO<\/a>
AUTHOR<\/a>
BUGS<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
void cleanup_module(void);<\/b><\/p>\nDESCRIPTION <\/a> <\/h2>\n
RETURN VALUE <\/a> <\/h2>\n
AVAILABILITY <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n
AUTHOR <\/a> <\/h2>\n