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

mlock.2: Describe treatment of MCL_FUTURE during fork(2) and execve(2) 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-04-14 10:19:45 +02:00
parent 49d2b31216
commit ec3b7804b3
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
man2/mlock.2
View File

@ -23,7 +23,7 @@
.\" <http://www.gnu.org/licenses/>.
.\" %%%LICENSE_END
.\"
.TH MLOCK 2 2011-09-14 "Linux" "Linux Programmer's Manual"
.TH MLOCK 2 2014-04-14 "Linux" "Linux Programmer's Manual"
.SH NAME
mlock, munlock, mlockall, munlockall \- lock and unlock memory
.SH SYNOPSIS
@ -247,6 +247,13 @@ Memory locks are not inherited by a child created via
and are automatically removed (unlocked) during an
.BR execve (2)
or when the process terminates.
The
.BR mlockall ()
.B MCL_FUTURE
setting is not inherited by a child created via
.BR fork (2)
and is cleared during an
.BR execve (2).
The memory lock on an address range is automatically removed
if the address range is unmapped via