In reality, almost every prctl interferes with assumptions that the compiler and C library / runtime rely on. prctl() can therefore make userspace explode in a variety ways that are likely to be hard to debug. This is not obvious to the uninitiated, so add a warning. Signed-off-by: Dave Martin <Dave.Martin@xxxxxxx> --- man2/prctl.2 | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/man2/prctl.2 b/man2/prctl.2 index 7932ada..a35b748 100644 --- a/man2/prctl.2 +++ b/man2/prctl.2 @@ -66,6 +66,11 @@ prctl \- operations on a process or thread manipulates various aspects of the behavior of the calling thread or process. .PP +Note that careless use of +.BR prctl () +can confuse the userspace run-time environment, +so these operations should be used with care (if at all). +.PP .BR prctl () is called with a first argument describing what to do (with values defined in \fI<linux/prctl.h>\fP), and further -- 2.1.4