LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

mmap.2: Minor wording fixes to to text describing MAP_FIXED hazards 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2018-04-13 08:50:38 +02:00
parent fd859eb599
commit 56a033affa
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
man2/mmap.2
View File

@ -249,11 +249,16 @@ If the specified address cannot be used,
.BR mmap ()
will fail.
.IP
Software that aspires to be portable should use this option with care,
Software that aspires to be portable should use the
.BR MAP_FIXED
flag with care,
keeping in mind that the exact layout of a process's memory mappings
is allowed to change significantly between kernel versions,
C library versions, and operating system releases.
This option should be used only when the specified memory region has
.IP
The
.BR MAP_FIXED
flag should be used only when the specified memory region has
already been reserved using another mapping; otherwise, it is extremely
hazardous because it forcibly removes preexisting mappings,
making it easy for a multithreaded process to corrupt its own address space.