Errata: Chapter 10, Signal and Interrupt Internals: read vs. write in PTRACE_POKEUSER explanation

[danilopiazza]

Chapter: 10
Description: The Signal and Interrupt Internals section on page 244 is possibly saying "read" instead of "write" when explaining how PTRACE_POKEUSER works:

The PTRACE_POKEUSER command gives the illusion that it’s writing a solid mapped region of memory, but on x64, this is actually a total lie. If you try to read anything that isn’t a GPR or debug register, it returns an error code.

Reproduction steps: No code errors, as this paragraph is explaining Linux kernel internals.

Assuming I am not getting confused, this would be a really minor oversight, and I almost feel sorry for reporting it.