/explore
|
You are here 
|
nickgregory.me | ||
| | | | |
binarydebt.wordpress.com
|
|
| | | | | System call table is an array of function pointers. It is defined in kernel space as variable sys_call_table and it contains pointers to functions which implement system calls. Index of each function pointer in the array is the system call number for that syscall. These are denoted by NR_* macros in header files, such as... | |
| | | | |
blog.osandov.com
|
|
| | | | | I just landed a really exciting feature for drgn: the ability to call arbitrary functions and write to memory in the Linux kernel. I think the technical details of the implementation are very interesting, and it's probably the funniest thing I've ever done, so I wanted to write about how it works. | |
| | | | |
xcellerator.github.io
|
|
| | | | | Okay, so you've built your first kernel module, but now you want to make it do something cool - something like altering the behaviour of the running kernel. The way we do this is by function hooking, but the question is - how do we know which functions to hook? Luckily for us, there is already a great list of potential targets: syscalls! Syscalls (or system calls) are kernel functions that can be called from userspace, and are required for almost anything remotely interesting. | |
| | | | |
bryanbrattlof.com
|
|
| | | Cave programmers carving Hello World on cave computers | ||
