mirror of https://github.com/mkerrisk/man-pages
mprotect.2: CONFORMING TO: note that pkey_mprotect() is Linux-specific
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
e956ced871
commit
8f5484f8b6
|
@ -136,6 +136,7 @@ in the middle of a region currently protected as
|
|||
would result in three mappings:
|
||||
two read/write mappings at each end and a read-only mapping in the middle.)
|
||||
.SH CONFORMING TO
|
||||
.BR mprotect ():
|
||||
POSIX.1-2001, POSIX.1-2008, SVr4.
|
||||
.\" SVr4 defines an additional error
|
||||
.\" code EAGAIN. The SVr4 error conditions don't map neatly onto Linux's.
|
||||
|
@ -144,6 +145,9 @@ POSIX says that the behavior of
|
|||
is unspecified if it is applied to a region of memory that
|
||||
was not obtained via
|
||||
.BR mmap (2).
|
||||
|
||||
.BR pkey_mprotect ()
|
||||
is a nonportable Linux extension.
|
||||
.SH NOTES
|
||||
On Linux, it is always permissible to call
|
||||
.BR mprotect ()
|
||||
|
|
Loading…
Reference in New Issue