Sfoglia il codice sorgente

Enforce consistent name scheme

Jim Huang 1 anno fa
parent
commit
e61a0d6174
3 ha cambiato i file con 3 aggiunte e 3 eliminazioni
  1. 1 1
      examples/Makefile
  2. 0 0
      examples/syscall-steal.c
  3. 2 2
      lkmpg.tex

+ 1 - 1
examples/Makefile

@@ -16,7 +16,7 @@ obj-m += print_string.o
 obj-m += kbleds.o
 obj-m += sched.o
 obj-m += chardev2.o
-obj-m += syscall_steal.o
+obj-m += syscall-steal.o
 obj-m += intrpt.o
 obj-m += cryptosha256.o
 obj-m += cryptosk.o

+ 0 - 0
examples/syscall_steal.c → examples/syscall-steal.c


+ 2 - 2
lkmpg.tex

@@ -1491,7 +1491,7 @@ $ sudo grep sys_call_table /proc/kallsyms
 ffffffff82000280 R x32_sys_call_table
 ffffffff820013a0 R sys_call_table
 ffffffff820023e0 R ia32_sys_call_table
-$ sudo insmod syscall_steal.ko sym=0xffffffff820013a0
+$ sudo insmod syscall-steal.ko sym=0xffffffff820013a0
 \end{verbatim}
 
 Using the address from \verb|/boot/System.map|, be careful about \verb|KASLR| (Kernel Address Space Layout Randomization).
@@ -1562,7 +1562,7 @@ Note that all the related problems make syscall stealing unfeasible for producti
 In order to keep people from doing potential harmful things \cpp|sys_call_table| is no longer exported.
 This means, if you want to do something more than a mere dry run of this example, you will have to patch your current kernel in order to have \cpp|sys_call_table| exported.
 
-\samplec{examples/syscall.c}
+\samplec{examples/syscall-steal.c}
 
 \section{Blocking Processes and threads}
 \label{sec:blocking_process_thread}