3rd-party/LKMPG
1
0
Fork 0
mirror of https://github.com/bashrc/LKMPG.git synced 2018-06-11 03:06:54 +02:00
Code Issues Releases Wiki Activity

proc_register_dynamic no longer appears to exist

Browse Source
This commit is contained in:
Bob Mottram
2017-08-03 10:34:17 +01:00
parent 133858b46f
commit 35c86517ca
2 changed files with 307 additions and 312 deletions
Download Patch File Download Diff File Expand all files Collapse all files

617
4.9.11/LKMPG-4.9.11.html
View File

File diff suppressed because it is too large Load Diff

2
4.9.11/LKMPG-4.9.11.org
View File

@@ -992,7 +992,7 @@ In Linux, there is an additional mechanism for the kernel and kernel modules to
The method to use the proc file system is very similar to the one used with device drivers --- a structure is created with all the information needed for the */proc* file, including pointers to any handler functions (in our case there is only one, the one called when somebody attempts to read from the */proc* file). Then, init_module registers the structure with the kernel and cleanup_module unregisters it.
The reason we use proc_register_dynamic[fn:8] is because we don't want to determine the inode number used for our file in advance, but to allow the kernel to determine it to prevent clashes. Normal file systems are located on a disk, rather than just in memory (which is where */proc* is), and in that case the inode number is a pointer to a disk location where the file's index-node (inode for short) is located. The inode contains information about the file, for example the file's permissions, together with a pointer to the disk location or locations where the file's data can be found.
Normal file systems are located on a disk, rather than just in memory (which is where */proc* is), and in that case the inode number is a pointer to a disk location where the file's index-node (inode for short) is located. The inode contains information about the file, for example the file's permissions, together with a pointer to the disk location or locations where the file's data can be found.
Because we don't get called when the file is opened or closed, there's nowhere for us to put try_module_get and try_module_put in this module, and if the file is opened and then the module is removed, there's no way to avoid the consequences.