| author | Chih-En Lin <shiyn.lin@gmail.com> | |
| Fri, 1 Jul 2022 13:09:38 +0000 (21:09 +0800) | ||
| committer | Chih-En Lin <shiyn.lin@gmail.com> | |
| Fri, 1 Jul 2022 13:31:08 +0000 (21:31 +0800) | ||
| commit | 3d1fb290705ed41fdd8417827f5556f71a0ec14a | |
| tree | b202f245582e44668dd53de0bb9c6e4996920810 | tree | snapshot |
| parent | 08eee1abf1230e0fb70ce8ca97553372cdb11f8d | commit | diff |
Add more information about the CFI of timer API
Currently, in 13.2 Flashing keyboard LEDs, the description of the
control-flow integrity, "Furthermore, the function prototype with
unsigned long argument may be an obstacle to the control-flow integrity
.", will confuse the reader.
It may lead the reader to think about hardware-assisted CFI like Intel
CET uses the shadow stack attack for ROP (backward-edge protection). But
the description of CFI here talks about the function pointer checking
with the prototype (forward-edge protection).
So add more information to make it more clear.
Close #151
Currently, in 13.2 Flashing keyboard LEDs, the description of the
control-flow integrity, "Furthermore, the function prototype with
unsigned long argument may be an obstacle to the control-flow integrity
.", will confuse the reader.
It may lead the reader to think about hardware-assisted CFI like Intel
CET uses the shadow stack attack for ROP (backward-edge protection). But
the description of CFI here talks about the function pointer checking
with the prototype (forward-edge protection).
So add more information to make it more clear.
Close #151
| lkmpg.tex | diff | blob | blame | history |