From f3edaabb5d0a5a232b9eff45a40c46f2f04ea95e Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Mon, 10 Sep 2007 04:10:36 +0000 Subject: [PATCH] Add text noting that PROT_WRITE may (and on x86 does) imply PROT_READ. --- man2/mmap.2 | 4 ++++ man2/mprotect.2 | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/man2/mmap.2 b/man2/mmap.2 index 7097ea9ce..e703ce77c 100644 --- a/man2/mmap.2 +++ b/man2/mmap.2 @@ -455,6 +455,10 @@ wrapper function invokes with a suitably adjusted value for .IR offset . +On some hardware architectures (e.g., x86), +.BR PROT_WRITE +implies +.BR PROT_READ . It is architecture dependent whether .B PROT_READ implies diff --git a/man2/mprotect.2 b/man2/mprotect.2 index f11affa04..a21f6507b 100644 --- a/man2/mprotect.2 +++ b/man2/mprotect.2 @@ -124,6 +124,10 @@ Whether has any effect different from .B PROT_READ is architecture and kernel version dependent. +On some hardware architectures (e.g., x86), +.BR PROT_WRITE +implies +.BR PROT_READ . POSIX.1-2001 says that an implementation may permit access other than that specified in