mirror of https://github.com/mkerrisk/man-pages
mlock.2: Document another ENOME error case
ENOMEM can occur if locking/unlocking in the middle of a region would increase the number of VMAs beyond the system limit (64k). Reported-by: Mehdi Aqadjani Memar <m.aqadjanimemar@student.vu.nl> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
8e085a68d0
commit
555c445244
|
@ -170,6 +170,15 @@ was not a multiple of the page size.
|
|||
.B ENOMEM
|
||||
Some of the specified address range does not correspond to mapped
|
||||
pages in the address space of the process.
|
||||
.TP
|
||||
.B ENOMEM
|
||||
Locking or unlocking a region would result in the total number of
|
||||
mappings with distinct attributes (e.g., locked versus unlocked)
|
||||
exceeding the allowed maximum.
|
||||
.\" I.e., the number of VMAs would exceed the 64kB maximum
|
||||
(For example, unlocking a range in the middle of a currently locked
|
||||
mapping would result in three mappings:
|
||||
two locked mappings at each end and an unlocked mapping in the middle.)
|
||||
.LP
|
||||
For
|
||||
.BR mlockall ():
|
||||
|
|
Loading…
Reference in New Issue