3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-26 19:51:35 +01:00
Code Issues Releases Wiki Activity

kprobes: mention CONFIG_KPROBE_EVENTS=y

Browse Source
This commit is contained in:
Ciro Santilli
2018-05-06 11:45:26 +01:00
parent 37743c40c3
commit 9db2d291ed
1 changed files with 11 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
README.adoc
View File

@@ -2222,10 +2222,10 @@ or with our shortcut:
/conf.sh /conf.sh
.... ....
or to conveniently grep for a specific option: or to conveniently grep for a specific option case insensitively:
.... ....
/conf.sh CONFIG_IKCONFIG /conf.sh ikconfig
.... ....
This is enabled by: This is enabled by:
@@ -2761,7 +2761,7 @@ echo function > current_tracer
# List all functions that can be traced # List all functions that can be traced
# cat available_filter_functions # cat available_filter_functions
# Choose one. # Choose one.
echo __kmalloc >set_ftrace_filter echo __kmalloc > set_ftrace_filter
# Confirm that only __kmalloc is enabled. # Confirm that only __kmalloc is enabled.
cat enabled_functions cat enabled_functions
@@ -2840,12 +2840,6 @@ TODO: can you get function arguments? https://stackoverflow.com/questions/276087
==== Kprobes ==== Kprobes
Inject arbitrary code at a given address in a trap instruction, much like GDB. Oh the good old kernel. :-)
I don't think your code can refer to the surrounding kernel code however: the only visible thing is the value of the registers.
Maybe you can then hack it up to read the stack and read argument values, but do you really want to?
.... ....
./build -c 'CONFIG_KPROBES=y' ./build -c 'CONFIG_KPROBES=y'
./run -F 'insmod /kprobe_example.ko && sleep 4 & sleep 4 &' ./run -F 'insmod /kprobe_example.ko && sleep 4 & sleep 4 &'
@@ -2862,6 +2856,14 @@ Outcome: every fork spits out some extra printks of type:
Docs: https://github.com/torvalds/linux/blob/v4.16/Documentation/kprobes.txt Docs: https://github.com/torvalds/linux/blob/v4.16/Documentation/kprobes.txt
Injects arbitrary code at a given address in a trap instruction, much like GDB. Oh the good old kernel. :-)
I don't think your code can refer to the surrounding kernel code however: the only visible thing is the value of the registers.
You can then hack it up to read the stack and read argument values, but do you really want to?
There is also a kprobes + ftrace based mechanism with `CONFIG_KPROBE_EVENTS=y` which does read the memory for us based on format strings that indicate type... https://github.com/torvalds/linux/blob/v4.16/Documentation/trace/kprobetrace.txt Horrendous. Used by: https://github.com/brendangregg/perf-tools/blob/98d42a2a1493d2d1c651a5c396e015d4f082eb20/execsnoop
==== Count boot instructions ==== Count boot instructions
* https://www.quora.com/How-many-instructions-does-a-typical-Linux-kernel-boot-take * https://www.quora.com/How-many-instructions-does-a-typical-Linux-kernel-boot-take