mprotect.2: mention effect of READ_IMPLIES_EXEC personality flag

I puzzled over mprotect()'s effect on /proc/*/maps for a while
yesterday -- it was setting "x" without PROT_EXEC being specified.
Here is a patch to add some explanation.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Mark Seaborn 2010-04-23 17:31:01 +01:00 committed by Michael Kerrisk
parent cae279c4d5
commit b22b377bd4
1 changed files with 9 additions and 1 deletions

View File

@ -130,7 +130,15 @@ Whether
.B PROT_EXEC
has any effect different from
.B PROT_READ
is architecture- and kernel version-dependent.
depends on processor architecture, kernel version, and process state. If
.B READ_IMPLIES_EXEC
is set in the process's personality flags (see
.BR personality (2)),
specifying
.B PROT_READ
will implicitly add
.BR PROT_EXEC.
On some hardware architectures (e.g., i386),
.B PROT_WRITE
implies