LINUX_VERSION_CODE
to the macro KERNEL_VERSION
. In version a.b.c of the kernel, the value of this macro would be 
.
- Normally, when you do not want to allow something, you return an error code
(a negative number) from the function which is supposed to do it. With
cleanup_module
- that’s impossible because it is a void function. However, there is a counter which
-keeps track of how many processes are using your module. You can see what its value
-is by looking at the 3rd field of /proc/modules. If this number isn’t zero,
- rmmod
+ that’s impossible because it is a void function. However, there is a counter
+which keeps track of how many processes are using your module. You
+can see what its value is by looking at the 3rd field with the command
+ cat /proc/modules
+ or sudo lsmod
+. If this number isn’t zero, rmmod
will fail. Note that you do not have to check the counter within
cleanup_module
because the check will be performed for you by the system call
@@ -1378,26 +1380,26 @@ decrease and display this counter:
try_module_get(THIS_MODULE)
- : Increment the use count.
+ : Increment the reference count of current module.
module_put(THIS_MODULE)
-
-
-
- : Decrement the use count.It is important to keep the counter accurate; if you ever do lose track of the + : Decrement the reference count of current module. + +
module_refcount(THIS_MODULE)
+ : Return the value of reference count of current module.It is important to keep the counter accurate; if you ever do lose track of the correct usage count, you will never be able to unload the module; it’s now reboot time, boys and girls. This is bound to happen to you sooner or later during a module’s development. -
+
The next code sample creates a char driver named chardev. You can cat its device +
The next code sample creates a char driver named chardev. You can cat its device file.
1cat /proc/devices-
(or open the file with a program) and the driver will put the number of times the +
(or open the file with a program) and the driver will put the number of times the
device file has been read from into the file. We do not support writing to the file (like
echo "hi" > /dev/hello
), but catch these attempts and tell the user that the operation is not supported.
@@ -1555,35 +1557,35 @@ acknowledging that we received it.
147module_exit(chardev_exit);
148
149MODULE_LICENSE("GPL");
-
+
The system calls, which are the major interface the kernel shows to the processes, +
The system calls, which are the major interface the kernel shows to the processes, generally stay the same across versions. A new system call may be added, but usually the old ones will behave exactly like they used to. This is necessary for backward compatibility – a new kernel version is not supposed to break regular -processes. In most cases, the device files will also remain the same. On the other -hand, the internal interfaces within the kernel can and do change between -versions. -
There are differences between different kernel versions, and if you want
-to support multiple kernel versions, you will find yourself having to code
-conditional compilation directives. The way to do this to compare the macro
- LINUX_VERSION_CODE
+processes. In most cases, the device files will also remain the same. On the other
+hand, the internal interfaces within the kernel can and do change between
+versions.
+
There are differences between different kernel versions, and if you want
+to support multiple kernel versions, you will find yourself having to code
+conditional compilation directives. The way to do this to compare the macro
+ LINUX_VERSION_CODE
to the macro KERNEL_VERSION
. In version a.b.c of the kernel, the value of this macro would be .
-
+
In Linux, there is an additional mechanism for the kernel and kernel modules to send +
In Linux, there is an additional mechanism for the kernel and kernel modules to send information to processes — the /proc file system. Originally designed to allow easy access to information about processes (hence the name), it is now used by every bit of the kernel which has something interesting to report, such as /proc/modules which provides the list of modules and /proc/meminfo which stats memory usage statistics. -
The method to use the proc file system is very similar to the one used with device +
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,
@@ -1591,34 +1593,34 @@ one called when somebody attempts to read from the cleanup_module
unregisters it.
-
Normal file systems are located on a disk, rather than just in memory (which is +
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 +
Because we don’t get called when the file is opened or closed, there’s nowhere for
us to put try_module_get
and 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.
-
Here a simple example showing how to use a /proc file. This is the HelloWorld for +
Here a simple example showing how to use a /proc file. This is the HelloWorld for
the /proc filesystem. There are three parts: create the file /proc/helloworld in the
function init_module
, return a value (and a buffer) when the file /proc/helloworld is read in the callback
function procfile_read
, and delete the file /proc/helloworld in the function
+
+
+
cleanup_module
.
-
The /proc/helloworld is created when the module is loaded with the function +
The /proc/helloworld is created when the module is loaded with the function
proc_create
. The return value is a struct proc_dir_entry
, and it will be used to configure the file /proc/helloworld (for example, the owner
of this file). A null return value means that the creation has failed.
-
-
-
-
Each time, everytime the file /proc/helloworld is read, the function +
Each time, everytime the file /proc/helloworld is read, the function
procfile_read
is called. Two parameters of this function are very important: the buffer
(the second parameter) and the offset (the fourth one). The content of the
@@ -1635,7 +1637,7 @@ function, if it never returns zero, the read function is called endlessly.
$ cat /proc/helloworld
HelloWorld!
-
+
1/* @@ -1710,10 +1712,10 @@ HelloWorld! 70module_exit(procfs1_exit); 71 72MODULE_LICENSE("GPL");-
+
The The proc_ops
+ as proc_ops
structure is defined in include/linux/proc_fs.h in Linux v5.6+. In older kernels, it
used file_operations
for custom hooks in /proc file system, but it contains some
@@ -1725,10 +1727,10 @@ performance. For example, the file which never disappears in proc_flag
PROC_ENTRY_PERMANENT
to save 2 atomic ops, 1 allocation, 1 free in per open/read/close sequence.
-
+
We have seen a very simple example for a /proc file where we only read +
We have seen a very simple example for a /proc file where we only read
the file /proc/helloworld. It is also possible to write in a /proc file. It
works the same way as read, a function is called when the /proc file
is written. But there is a little difference with read, data comes from
@@ -1736,7 +1738,7 @@ user, so you have to import data from user space to kernel space (with
copy_from_user
or get_user
)
-
The reason for copy_from_user
+
The reason for copy_from_user
or get_user
is that Linux memory (on Intel architecture, it may be different under some
@@ -1747,7 +1749,7 @@ not reference a unique location in memory, only a location in a memory
segment, and you need to know which memory segment it is to be able to use
it. There is one memory segment for the kernel, and one for each of the
processes.
-
The only memory segment accessible to a process is its own, so when +
The only memory segment accessible to a process is its own, so when writing regular programs to run as processes, there is no need to worry about segments. When you write a kernel module, normally you want to access the kernel memory segment, which is handled automatically by the system. @@ -1864,22 +1866,22 @@ because data is already in kernel space. 97module_exit(procfs2_exit); 98 99MODULE_LICENSE("GPL"); -
+
We have seen how to read and write a /proc file with the /proc interface. But it is +
We have seen how to read and write a /proc file with the /proc interface. But it is also possible to manage /proc file with inodes. The main concern is to use advanced functions, like permissions. -
In Linux, there is a standard mechanism for file system registration. +
In Linux, there is a standard mechanism for file system registration.
Since every file system has to have its own functions to handle inode and file
operations, there is a special structure to hold pointers to all those functions,
struct inode_operations
, which includes a pointer to struct proc_ops
.
-
The difference between file and inode operations is that file operations deal with +
The difference between file and inode operations is that file operations deal with the file itself whereas inode operations deal with ways of referencing the file, such as creating links to it. -
In /proc, whenever we register a new file, we’re allowed to specify which +
In /proc, whenever we register a new file, we’re allowed to specify which
struct inode_operations
will be used to access to it. This is the mechanism we use, a
struct inode_operations
@@ -1890,7 +1892,7 @@ creating links to it.
which includes pointers to our procf_read
and procfs_write
functions.
-
Another interesting point here is the +
Another interesting point here is the
module_permission
function. This function is called whenever a process tries to do something with the
/proc file, and it can decide whether to allow access or not. Right now it is only
@@ -1899,7 +1901,7 @@ pointer to a structure which includes information on the currently running
process), but it could be based on anything we like, such as what other
processes are doing with the same file, the time of day, or the last input we
received.
-
It is important to note that the standard roles of read and write are reversed in +
It is important to note that the standard roles of read and write are reversed in the kernel. Read functions are used for output, whereas write functions are used for input. The reason for that is that read and write refer to the user’s point of view — if a process reads something from the kernel, then the kernel needs to output it, and @@ -2014,14 +2016,14 @@ input. 105module_exit(procfs3_exit); 106 107MODULE_LICENSE("GPL"); -
Still hungry for procfs examples? Well, first of all keep in mind, there are rumors +
Still hungry for procfs examples? Well, first of all keep in mind, there are rumors around, claiming that procfs is on its way out, consider using sysfs instead. Consider using this mechanism, in case you want to document something kernel related yourself. -
+
As we have seen, writing a /proc file may be quite “complex”. +
As we have seen, writing a /proc file may be quite “complex”.
So to help people writting /proc file, there is an API named
seq_file
that helps formating a /proc file for output. It is based on sequence, which is composed of
@@ -2030,7 +2032,7 @@ So to help people writting , and stop()
. The seq_file
API starts a sequence when a user read the /proc file.
-
A sequence begins with the call of the function +
A sequence begins with the call of the function
start()
. If the return is a non NULL
value, the function next()
@@ -2047,7 +2049,7 @@ time next()
returns NULL
, then the function stop()
is called.
-
BE CAREFUL: when a sequence is finished, another one starts. That means that at the end +
BE CAREFUL: when a sequence is finished, another one starts. That means that at the end
of function The The If you want more information, you can read this web page:
+ If you want more information, you can read this web page:
You can also read the code of fs/seq_file.c in the linux kernel.
+ You can also read the code of fs/seq_file.c in the linux kernel.
sysfs allows you to interact with the running kernel from userspace by reading or
+ sysfs allows you to interact with the running kernel from userspace by reading or
setting variables inside of modules. This can be useful for debugging purposes, or just
as an interface for applications or scripts. You can find sysfs directories and files
under the /sys directory on your system.
An example of a hello world module which includes the creation of a variable
+ An example of a hello world module which includes the creation of a variable
accessible via sysfs is given below.
Make and install the module:
+ Make and install the module:
Check that it exists:
+ Check that it exists:
What is the current value of What is the current value of
Set the value of Set the value of
Finally, remove the test module:
+ Finally, remove the test module:
+
Device files are supposed to represent physical devices. Most physical devices are
+ Device files are supposed to represent physical devices. Most physical devices are
used for output as well as input, so there has to be some mechanism for
device drivers in the kernel to get the output to send to the device from
processes. This is done by opening the device file for output and writing to it,
just like writing to a file. In the following example, this is implemented by
This is not always enough. Imagine you had a serial port connected to a modem
+ This is not always enough. Imagine you had a serial port connected to a modem
(even if you have an internal modem, it is still implemented from the CPU’s
perspective as a serial port connected to a modem, so you don’t have to tax
your imagination too hard). The natural thing to do would be to use the
@@ -2330,7 +2332,7 @@ received.
- The answer in Unix is to use a special function called
+ The answer in Unix is to use a special function called
The ioctl function is called with three parameters: the file descriptor of the
+ The ioctl function is called with three parameters: the file descriptor of the
appropriate device file, the ioctl number, and a parameter, which is of type
long so you can use a cast to use it to pass anything. You will not be able
to pass a structure this way, but you will be able to pass a pointer to the
structure.
- The ioctl number encodes the major device number, the type of the ioctl, the
+ The ioctl number encodes the major device number, the type of the ioctl, the
command, and the type of the parameter. This ioctl number is usually created by a macro
call ( If you want to use ioctls in your own kernel modules, it is best to receive an
+ If you want to use ioctls in your own kernel modules, it is best to receive an
official ioctl assignment, so if you accidentally get somebody else’s ioctls, or if they
get yours, you’ll know something is wrong. For more information, consult the kernel
source tree at Documentation/driver-api/ioctl.rst.
@@ -2841,18 +2843,18 @@ source tree at 196
197MODULE_LICENSE("GPL");
198MODULE_DESCRIPTION("This is test_ioctl module");
+
So far, the only thing we’ve done was to use well defined kernel mechanisms to
+ So far, the only thing we’ve done was to use well defined kernel mechanisms to
register /proc files and device handlers. This is fine if you want to do something the
kernel programmers thought you’d want, such as write a device driver. But what if
you want to do something unusual, to change the behavior of the system in some
way? Then, you are mostly on your own.
- If you are not being sensible and using a virtual machine then this is where kernel
+ If you are not being sensible and using a virtual machine then this is where kernel
programming can become hazardous. While writing the example below, I killed the
Forget about /proc files, forget about device files. They are just minor details.
+ Forget about /proc files, forget about device files. They are just minor details.
Minutiae in the vast expanse of the universe. The real process to kernel
communication mechanism, the one used by all processes, is system calls. When a
process requests a service from the kernel (such as opening a file, forking to a new
@@ -2873,11 +2875,11 @@ change the behaviour of the kernel in interesting ways, this is the place to do
it. By the way, if you want to see which system calls a program uses, run
In general, a process is not supposed to be able to access the kernel. It can not
+ In general, a process is not supposed to be able to access the kernel. It can not
access kernel memory and it can’t call kernel functions. The hardware of the CPU
enforces this (that is the reason why it is called “protected mode” or “page
protection”).
- System calls are an exception to this general rule. What happens is that the
+ System calls are an exception to this general rule. What happens is that the
process fills the registers with the appropriate values and then calls a special
instruction which jumps to a previously defined location in the kernel (of course, that
location is readable by user processes, it is not writable by them). Under Intel CPUs,
@@ -2885,7 +2887,7 @@ this is done by means of interrupt 0x80. The hardware knows that once you jump t
this location, you are no longer running in restricted user mode, but as the
operating system kernel — and therefore you’re allowed to do whatever you
want.
- The location in the kernel a process can jump to is called system_call. The
+ The location in the kernel a process can jump to is called system_call. The
procedure at that location checks the system call number, which tells the kernel what
service the process requested. Then, it looks at the table of system calls
( So, if we want to change the way a certain system call works, what we need to do
+ So, if we want to change the way a certain system call works, what we need to do
is to write our own function to implement it (usually by adding a bit of our own
code, and then calling the original function) and then change the pointer at
The source code here is an example of such a kernel module. We want to “spy” on a certain
+ The source code here is an example of such a kernel module. We want to “spy” on a certain
user, and to The The Now, if B is removed first, everything will be well — it will simply restore the system
+ Now, if B is removed first, everything will be well — it will simply restore the system
call to Note that all the related problems make syscall stealing unfeasiable for
+ Note that all the related problems make syscall stealing unfeasiable for
production use. In order to keep people from doing potential harmful things
+
+
What do you do when somebody asks you for something you can not do right
+ What do you do when somebody asks you for something you can not do right
away? If you are a human being and you are bothered by a human being, the
only thing you can say is: "Not right now, I’m busy. Go away!". But if you
are a kernel module and you are bothered by a process, you have another
@@ -3125,21 +3127,21 @@ processes are being put to sleep by the kernel and woken up all the time (that
is the way multiple processes appear to run on the same time on a single
CPU).
- This kernel module is an example of this. The file (called /proc/sleep) can only
+ This kernel module is an example of this. The file (called /proc/sleep) can only
be opened by a single process at a time. If the file is already open, the kernel module
calls
This function changes the status of the task (a task is the kernel data structure
+ This function changes the status of the task (a task is the kernel data structure
which holds information about a process and the system call it is in, if any) to
When a process is done with the file, it closes it, and
+ When a process is done with the file, it closes it, and
This means that the process is still in kernel mode - as far as the process
+ This means that the process is still in kernel mode - as far as the process
is concerned, it issued the open system call and the system call has not
returned yet. The process does not know somebody else used the CPU for
most of the time between the moment it issued the call and the moment it
returned.
- It can then proceed to set a global variable to tell all the other processes that the
+ It can then proceed to set a global variable to tell all the other processes that the
file is still open and go on with its life. When the other processes get a piece of the
CPU, they’ll see that global variable and go back to sleep.
- So we will use So we will use To make our life more interesting, To make our life more interesting, In that case, we want to return with
+ In that case, we want to return with
There is one more point to remember. Some times processes don’t want to sleep, they want
+ There is one more point to remember. Some times processes don’t want to sleep, they want
either to get what they want immediately, or to be told it cannot be done. Such processes
use the
+
+
Sometimes one thing should happen before another within a module having multiple threads.
+ Sometimes one thing should happen before another within a module having multiple threads.
Rather than using In the following example two threads are started, but one needs to start before
+ In the following example two threads are started, but one needs to start before
another.
@@ -3586,31 +3588,31 @@ another.
74
75MODULE_DESCRIPTION("Completions example");
76MODULE_LICENSE("GPL");
- The The So even though So even though There are other variations upon the
+ There are other variations upon the
+
If processes running on different CPUs or in different threads try to access the same
+ If processes running on different CPUs or in different threads try to access the same
memory, then it is possible that strange things can happen or your system can lock
up. To avoid this, various types of mutual exclusion kernel functions are available.
These indicate if a section of code is "locked" or "unlocked" so that simultaneous
attempts to run it can not happen.
You can use kernel mutexes (mutual exclusions) in much the same manner that you
+ You can use kernel mutexes (mutual exclusions) in much the same manner that you
might deploy them in userland. This may be all that is needed to avoid collisions in
most cases.
@@ -3656,10 +3658,10 @@ most cases.
39
40MODULE_DESCRIPTION("Mutex example");
41MODULE_LICENSE("GPL");
-
+
As the name suggests, spinlocks lock up the CPU that the code is running on,
+ As the name suggests, spinlocks lock up the CPU that the code is running on,
taking 100% of its resources. Because of this you should only use the spinlock
@@ -3667,7 +3669,7 @@ taking 100% of its resources. Because of this you should only use the spinlock
mechanism around code which is likely to take no more than a few milliseconds to
run and so will not noticably slow anything down from the user’s point of
view.
- The example here is "irq safe" in that if interrupts happen during the lock then
+ The example here is "irq safe" in that if interrupts happen during the lock then
they will not be forgotten and will activate when the unlock happens, using the
+
Read and write locks are specialised kinds of spinlocks so that you can exclusively
+ Read and write locks are specialised kinds of spinlocks so that you can exclusively
read from something or write to something. Like the earlier spinlocks example, the
one below shows an "irq safe" situation in which if other functions were triggered
from irqs which might also read and write to whatever you are concerned with
@@ -3804,14 +3806,14 @@ module.
53
54MODULE_DESCRIPTION("Read/Write locks example");
55MODULE_LICENSE("GPL");
- Of course, if you know for sure that there are no functions triggered by irqs
+ Of course, if you know for sure that there are no functions triggered by irqs
which could possibly interfere with your logic then you can use the simpler
If you are doing simple arithmetic: adding, subtracting or bitwise operations, then
+ If you are doing simple arithmetic: adding, subtracting or bitwise operations, then
there is another way in the multi-CPU and multi-hyperthreaded world to stop other
parts of the system from messing with your mojo. By using atomic operations you
can be confident that your addition, subtraction or bit flip did actually happen
@@ -3896,21 +3898,21 @@ below.
-
+
+
In Section 2, I said that X Window System and kernel module programming do not
+ In Section 2, I said that X Window System and kernel module programming do not
mix. That is true for developing kernel modules. But in actual use, you want to be
able to send messages to whichever tty the command to load the module came
from.
- "tty" is an abbreviation of teletype: originally a combination keyboard-printer
+ "tty" is an abbreviation of teletype: originally a combination keyboard-printer
used to communicate with a Unix system, and today an abstraction for the text
stream used for a Unix program, whether it is a physical terminal, an xterm on an X
display, a network connection used with ssh, etc.
- The way this is done is by using current, a pointer to the currently running task,
+ The way this is done is by using current, a pointer to the currently running task,
to get the current task’s tty structure. Then, we look inside that tty structure to find
a pointer to a string write function, which we use to write a string to the
tty.
@@ -3993,16 +3995,16 @@ tty.
75module_exit(print_string_exit);
76
77MODULE_LICENSE("GPL");
-
+
In certain conditions, you may desire a simpler and more direct way to communicate
+ In certain conditions, you may desire a simpler and more direct way to communicate
to the external world. Flashing keyboard LEDs can be such a solution: It is an
immediate way to attract attention or to display a status condition. Keyboard LEDs
are present on every hardware, they are always visible, they do not need any setup,
and their use is rather simple and non-intrusive, compared to writing to a tty or a
file.
- The following source code illustrates a minimal kernel module which, when
+ The following source code illustrates a minimal kernel module which, when
loaded, starts blinking the keyboard LEDs until it is unloaded.
If none of the examples in this chapter fit your debugging needs,
+ If none of the examples in this chapter fit your debugging needs,
there might yet be some other tricks to try. Ever wondered what
While you have seen lots of stuff that can be used to aid debugging here, there are
+ While you have seen lots of stuff that can be used to aid debugging here, there are
some things to be aware of. Debugging is almost always intrusive. Adding debug code
can change the situation enough to make the bug seem to dissappear. Thus you
should try to keep debug code to a minimum and make sure it does not show up in
production code.
-
+
There are two main ways of running tasks: tasklets and work queues. Tasklets are a
+ There are two main ways of running tasks: tasklets and work queues. Tasklets are a
quick and easy way of scheduling a single function to be run. For example, when
triggered from an interrupt, whereas work queues are more complicated but also
better suited to running multiple things in a sequence.
-
+
Here is an example tasklet module. The
+ Here is an example tasklet module. The
So with this example loaded So with this example loaded
-
+
+
To add a task to the scheduler we can use a workqueue. The kernel then uses the
+ To add a task to the scheduler we can use a workqueue. The kernel then uses the
Completely Fair Scheduler (CFS) to execute work within the queue.
+
+
Except for the last chapter, everything we did in the kernel so far we have done as a
+ Except for the last chapter, everything we did in the kernel so far we have done as a
response to a process asking for it, either by dealing with a special file, sending an
There are two types of interaction between the CPU and the rest of the
+ There are two types of interaction between the CPU and the rest of the
computer’s hardware. The first type is when the CPU gives orders to the hardware,
the order is when the hardware needs to tell the CPU something. The second, called
interrupts, is much harder to implement because it has to be dealt with when
@@ -4244,14 +4246,14 @@ lost.
- Under Linux, hardware interrupts are called IRQ’s (Interrupt ReQuests). There
+ Under Linux, hardware interrupts are called IRQ’s (Interrupt ReQuests). There
are two types of IRQ’s, short and long. A short IRQ is one which is expected to take
a very short period of time, during which the rest of the machine will be blocked and
no other interrupts will be handled. A long IRQ is one which can take longer, and
during which other interrupts may occur (but not interrupts from the same
device). If at all possible, it is better to declare an interrupt handler to be
long.
- When the CPU receives an interrupt, it stops whatever it is doing (unless it is
+ When the CPU receives an interrupt, it stops whatever it is doing (unless it is
processing a more important interrupt, in which case it will deal with this one
only when the more important one is done), saves certain parameters on
the stack and calls the interrupt handler. This means that certain things
@@ -4263,10 +4265,10 @@ the new information at a later time (this is called the "bottom half") and
return. The kernel is then guaranteed to call the bottom half as soon as
possible – and when it does, everything allowed in kernel modules will be
allowed.
- The way to implement this is to call
+ The way to implement this is to call
In practice IRQ handling can be a bit more complex. Hardware is often
+ In practice IRQ handling can be a bit more complex. Hardware is often
designed in a way that chains two interrupt controllers, so that all the IRQs
from interrupt controller B are cascaded to a certain IRQ from interrupt
controller A. Of course, that requires that the kernel finds out which IRQ it
@@ -4280,7 +4282,7 @@ need to solve another truckload of problems. It is not enough to know if
a certain IRQs has happend, it’s also important for what CPU(s) it was
for. People still interested in more details, might want to refer to "APIC"
now.
- This function receives the IRQ number, the name of the function,
+ This function receives the IRQ number, the name of the function,
flags, a name for /proc/interrupts and a parameter to be passed to the
interrupt handler. Usually there is a certain number of IRQs available.
How many IRQs there are is hardware-dependent. The flags can include
@@ -4293,16 +4295,16 @@ already a handler on this IRQ, or if you are both willing to share.
-
+
Many popular single board computers, such as Raspberry Pi or Beagleboards, have a
+ Many popular single board computers, such as Raspberry Pi or Beagleboards, have a
bunch of GPIO pins. Attaching buttons to those and then having a button press do
something is a classic case in which you might need to use interrupts, so that instead
of having the CPU waste time and battery power polling for a change in input state,
it is better for the input to trigger the CPU to then run a particular handling
function.
- Here is an example where buttons are connected to GPIO numbers 17 and 18 and
+ Here is an example where buttons are connected to GPIO numbers 17 and 18 and
an LED is connected to GPIO 4. You can change those numbers to whatever is
appropriate for your board.
@@ -4452,14 +4454,14 @@ appropriate for your board.
143
144MODULE_LICENSE("GPL");
145MODULE_DESCRIPTION("Handle some GPIO interrupts");
-
+
Suppose you want to do a bunch of stuff inside of an interrupt routine. A common
+ Suppose you want to do a bunch of stuff inside of an interrupt routine. A common
way to do that without rendering the interrupt unavailable for a significant duration
is to combine it with a tasklet. This pushes the bulk of the work off into the
scheduler.
- The example below modifies the previous example to also run an additional task
+ The example below modifies the previous example to also run an additional task
when an interrupt is triggered.
+
At the dawn of the internet, everybody trusted everybody completely…but that did
+ At the dawn of the internet, everybody trusted everybody completely…but that did
not work out so well. When this guide was originally written, it was a more innocent
era in which almost nobody actually gave a damn about crypto - least of all kernel
developers. That is certainly no longer the case now. To handle crypto stuff, the
@@ -4636,10 +4638,10 @@ favourite hash functions.
-
+
Calculating and checking the hashes of things is a common operation. Here is a
+ Calculating and checking the hashes of things is a common operation. Here is a
demonstration of how to calculate a sha256 hash within a kernel module.
Make and install the module:
+ Make and install the module:
And you should see that the hash was calculated for the test string.
- Finally, remove the test module:
+ And you should see that the hash was calculated for the test string.
+ Finally, remove the test module:
+
Here is an example of symmetrically encrypting a string using the AES algorithm
+ Here is an example of symmetrically encrypting a string using the AES algorithm
and a password.
+
Up to this point we have seen all kinds of modules doing all kinds of things, but there
+ Up to this point we have seen all kinds of modules doing all kinds of things, but there
was no consistency in their interfaces with the rest of the kernel. To impose some
consistency such that there is at minimum a standardized way to start, suspend and
resume a device a device model was added. An example is show below, and you can
@@ -5033,13 +5035,13 @@ functions.
-
+
+
Sometimes you might want your code to run as quickly as possible,
+ Sometimes you might want your code to run as quickly as possible,
especially if it is handling an interrupt or doing something which might
cause noticible latency. If your code contains boolean conditions and if you
know that the conditions are almost always likely to evaluate as either
@@ -5049,7 +5051,7 @@ know that the conditions are almost always likely to evaluate as either
For example, when allocating memory you are almost always expecting this to
+ For example, when allocating memory you are almost always expecting this to
succeed.
When the When the
+
+
You can not do that. In a kernel module, you can only use kernel functions which are
+ You can not do that. In a kernel module, you can only use kernel functions which are
the functions you can see in /proc/kallsyms.
-
+
You might need to do this for a short time and that is OK, but if you do not enable
+ You might need to do this for a short time and that is OK, but if you do not enable
them afterwards, your system will be stuck and you will have to power it
off.
-
+
For people seriously interested in kernel programming, I recommend kernelnewbies.org
+ For people seriously interested in kernel programming, I recommend kernelnewbies.org
and the Documentation subdirectory within the kernel source code which is not
always easy to understand but can be a starting point for further investigation. Also,
as Linus Torvalds said, the best way to learn the kernel is to read the source code
yourself.
- If you are interested in more examples of short kernel modules then searching on
+ If you are interested in more examples of short kernel modules then searching on
sites such as Github and Gitlab is a good way to start, although there is a lot of
duplication of older LKMPG examples which may not compile with newer kernel
versions. You will also be able to find examples of the use of kernel modules to attack
or compromise systems or exfiltrate data and those can be useful for thinking about
how to defend systems and learning about existing security mechanisms within the
kernel.
- I hope I have helped you in your quest to become a better programmer, or at
+ I hope I have helped you in your quest to become a better programmer, or at
least to have fun through technology. And, if you do write useful kernel modules, I
hope you publish them under the GPL, so I can use them too.
- If you would like to contribute to this guide or notice anything glaringly wrong,
+ If you would like to contribute to this guide or notice anything glaringly wrong,
please create an issue at https://github.com/sysprog21/lkmpg.
- Happy hacking!
+ Happy hacking!
stop()
, the function start()
is called again. This loop finishes when the function
@@ -2064,14 +2066,14 @@ of function stop()
-
+
seq_file
+ will still try to call seq_file
provides basic functions for proc_ops
, such as seq_read
, seq_lseek
@@ -2195,23 +2197,23 @@ the same way as in the previous example.
115module_exit(procfs4_exit);
116
117MODULE_LICENSE("GPL");
- right before you do the 0.8 sysfs: Interacting with your module
-1ls -l /sys
-1make
@@ -2288,36 +2290,36 @@ accessible via sysfs is given below.
-
-1sudo lsmod | grep hello_sysfs
- myvariable
+ myvariable
?
1cat /sys/kernel/mymodule/myvariable
- myvariable
+ myvariable
and check that it changed.
1echo "32" > /sys/kernel/mymodule/myvariable
2cat /sys/kernel/mymodule/myvariable
-1sudo rmmod hello_sysfs
-0.9 Talking To Device Files
- device_write
.
- ioctl
(short for Input Output ConTroL). Every device can have its own
ioctl
@@ -2339,12 +2341,12 @@ kernel), write ioctl’s (to return information to a process), both or neither.
here the roles of read and write are reversed again, so in ioctl’s read is to
send information to the kernel and write is to receive information from the
kernel.
- _IO
, _IOR
@@ -2355,7 +2357,7 @@ included both by the programs which will use ioctl (so they can generate the
appropriate ioctl’s) and by the kernel module (so it can understand it). In the
example below, the header file is chardev.h and the program which uses it is
ioctl.c.
-0.10 System Calls
- open()
system call. This meant I could not open any files, I could not run any
@@ -2864,7 +2866,7 @@ ensure you do not lose any files, even within a test environment, please run
insmod
and the rmmod
.
- strace <arguments>
.
- sys_call_table
@@ -2898,7 +2900,7 @@ different process, if the process time ran out). If you want to read this code,
at the source file arch/$(architecture)/kernel/entry.S, after the line
ENTRY(system_call)
.
- sys_call_table
@@ -2906,7 +2908,7 @@ code, and then calling the original function) and then change the pointer at
don’t want to leave the system in an unstable state, it’s important for
cleanup_module
to restore the table to its original state.
- pr_info()
a message whenever that user opens a file. Towards this end, we
replace the system call to open a file with our own function, called
@@ -2916,7 +2918,7 @@ spy on, it calls pr_info()
to display the name of the file to be opened. Then, either way, it calls the original
open()
function with the same parameters, to actually open the file.
- init_module
+ init_module
function replaces the appropriate location in
sys_call_table
and keeps the original pointer in a variable. The
@@ -2934,7 +2936,7 @@ with B_open
, which will call what it thinks is the original system call,
A_open
, when it’s done.
- A_open
, which calls the original. However, if A is removed and then B is removed, the
system will crash. A’s removal will restore the system call to the original,
@@ -2957,7 +2959,7 @@ problem. When A is removed, it sees that the system call was changed to
A_open
which is no longer there, so that even without removing B the system would
crash.
- sys_call_table
is no longer exported. This means, if you want to do something more than a mere
@@ -3108,13 +3110,13 @@ hand apply the patch.
135module_exit(syscall_end);
136
137MODULE_LICENSE("GPL");
-0.11 Blocking Processes and threads
-0.11.1 Sleep
- wait_event_interruptible
. The easiest way to keep a file open is to open it with:
1tail -f
- TASK_INTERRUPTIBLE
, which means that the task will not run until it is woken up somehow, and adds it to
WaitQ, the queue of tasks waiting to access the file. Then, the function calls the
scheduler to context switch to a different process, one which has some use for the
CPU.
- module_close
is called. That function wakes up all the processes in the queue (there’s no
mechanism to only wake up one of them). It then returns and the process which just
@@ -3149,20 +3151,20 @@ Eventually, one of the processes which was in the queue will be given control
of the CPU by the scheduler. It starts at the point right after the call to
module_interruptible_sleep_on
.
- tail -f
+ tail -f
to keep the file open in the background, while trying to access it with another
process (again in the background, so that we need not switch to a different vt). As
soon as the first background process is killed with kill %1 , the second is woken up, is
able to access the file and finally terminates.
- module_close
+ module_close
does not have a monopoly on waking up the processes which wait to access the file.
A signal, such as Ctrl +c (SIGINT) can also wake up a process. This is because we
used module_interruptible_sleep_on
@@ -3172,11 +3174,11 @@ used module_interruptible_sleep_on
instead, but that would have resulted in extremely angry users whose Ctrl+c’s are
ignored.
- -EINTR
immediately. This is important so users can, for example, kill the process before it
receives the file.
- O_NONBLOCK
flag when opening the file. The kernel is supposed to respond by returning with the error
@@ -3212,7 +3214,7 @@ $ cat_nonblock /proc/sleep
Last input:
$
-1/*
@@ -3496,14 +3498,14 @@ $
57
58 return 0;
59}
-0.11.2 Completions
- /bin/sleep
commands, the kernel has another way to do this which allows timeouts or
interrupts to also happen.
- machine
+ machine
structure stores the completion states for the two threads. At the exit
point of each thread the respective completion state is updated, and
wait_for_completion
is used by the flywheel thread to ensure that it does not begin prematurely.
- flywheel_thread
+ flywheel_thread
is started first you should notice if you load this module and run
dmesg
that turning the crank always happens first because the flywheel thread waits for it
to complete.
- wait_for_completion
function, which include timeouts or being interrupted, but this basic mechanism is
enough for many common situations without adding a lot of complexity.
-0.12 Avoiding Collisions and Deadlocks
-0.12.1 Mutex
-0.12.2 Spinlocks
- flags
variable to retain their state.
@@ -3736,10 +3738,10 @@ they will not be forgotten and will activate when the unlock happens, using the
61
62MODULE_DESCRIPTION("Spinlock example");
63MODULE_LICENSE("GPL");
-0.12.3 Read and write locks
- read_lock(&myrwlock)
and read_unlock(&myrwlock)
or the corresponding write functions.
0.12.4 Atomic operations
-0.13 Replacing Print Macros
-0.13.1 Replacement
-0.13.2 Flashing keyboard LEDs
- CONFIG_LL_DEBUG
in make menuconfig
@@ -4109,22 +4111,22 @@ everything what your code does over a serial line. If you find yourself porting
kernel to some new and former unsupported architecture, this is usually amongst the
first things that should be implemented. Logging over a netconsole might also be
worth a try.
-0.14 Scheduling Tasks
-0.14.1 Tasklets
- tasklet_fn
function runs for a few seconds and in the mean time execution of the
example_tasklet_init
@@ -4168,7 +4170,7 @@ better suited to running multiple things in a sequence.
35
36MODULE_DESCRIPTION("Tasklet example");
37MODULE_LICENSE("GPL");
- dmesg
+ dmesg
should show:
@@ -4180,11 +4182,11 @@ Example tasklet starts
Example tasklet init continues...
Example tasklet ends
-0.14.2 Work queues
-0.15 Interrupt Handlers
-0.15.1 Interrupt Handlers
- ioctl()
, or issuing a system call. But the job of the kernel is not just to respond to process
requests. Another job, which is every bit as important, is to speak to the hardware
connected to the machine.
- request_irq()
to get your interrupt handler called when the relevant IRQ is received.
-0.15.2 Detecting button presses
-0.15.3 Bottom Half
-0.16 Crypto
-0.16.1 Hash functions
-1make
2sudo insmod cryptosha256.ko
3dmesg
-1sudo rmmod cryptosha256
-0.16.2 Symmetric key encryption
-0.17 Standardizing the interfaces: The Device Model
-0.18 Optimizations
-0.18.1 Likely and Unlikely conditions
- likely
and unlikely
macros.
- unlikely
+ unlikely
macro is used, the compiler alters its machine instruction output, so that it
continues along the false branch and only jumps if the condition is true. That
avoids flushing the processor pipeline. The opposite happens if you use the
likely
macro.
-0.19 Common Pitfalls
-0.19.1 Using standard libraries
-0.19.2 Disabling interrupts
-0.20 Where To Go From Here?
-