Re PTRACE_PEEKUSER: the offsets and data returned might not

match with the defintion of struct user.

man2/ptrace.2

@@ -40,7 +40,7 @@
 .\"        PTRACE_SETSIGINFO, PTRACE_SYSEMU, PTRACE_SYSEMU_SINGLESTEP
 .\"    (Thanks to Blaisorblade, Daniel Jacobowitz and others who helped.)
 .\"
-.TH PTRACE 2 2007-11-15 "Linux" "Linux Programmer's Manual"
+.TH PTRACE 2 2008-05-21 "Linux" "Linux Programmer's Manual"
 .SH NAME
 ptrace \- process trace
 .SH SYNOPSIS
@@ -138,7 +138,9 @@ The word is returned as the result of the
 .BR ptrace ()
 call.
 Typically the offset must be word-aligned, though this might vary by
-architecture.  (\fIdata\fP is ignored.)
+architecture.
+See NOTES.
+(\fIdata\fP is ignored.)
 .TP
 .BR PTRACE_POKETEXT ", " PTRACE_POKEDATA
 Copies the word
@@ -191,7 +193,8 @@ the child and were caught by the tracer.
 It may be difficult to tell
 these normal signals from synthetic signals generated by
 .BR ptrace ()
-itself.  (\fIaddr\fP is ignored.)
+itself.
+(\fIaddr\fP is ignored.)
 .TP
 .BR PTRACE_SETOPTIONS " (since Linux 2.4.6; see BUGS for caveats)"
 Sets ptrace options from \fIdata\fP in the parent.
@@ -455,6 +458,10 @@ the process with PID 1, may not be traced.
 .LP
 The layout of the contents of memory and the USER area are quite OS- and
 architecture-specific.
+The offset supplied, and the data returned,
+might not entirely match with the definition of
+.IR "struct user" .
+.\" See http://lkml.org/lkml/2008/5/8/375
 .LP
 The size of a "word" is determined by the OS variant
 (e.g., for 32-bit Linux it is 32 bits, etc.).