summaryrefslogtreecommitdiffstats
path: root/share/man/man9/vslock.9
diff options
context:
space:
mode:
authorgreen <green@FreeBSD.org>2004-08-10 15:01:00 +0000
committergreen <green@FreeBSD.org>2004-08-10 15:01:00 +0000
commit7419bfcbfbb383fd5850b9b64f04a1c900de46b3 (patch)
treeed2375c4779a2c3c837ec47918c2b5cd907992e3 /share/man/man9/vslock.9
parent94edfa59ed028a1711a8492bbc0818247c5c73c7 (diff)
downloadFreeBSD-src-7419bfcbfbb383fd5850b9b64f04a1c900de46b3.zip
FreeBSD-src-7419bfcbfbb383fd5850b9b64f04a1c900de46b3.tar.gz
Document exactly how vslock(9) is broken.
Diffstat (limited to 'share/man/man9/vslock.9')
-rw-r--r--share/man/man9/vslock.96
1 files changed, 6 insertions, 0 deletions
diff --git a/share/man/man9/vslock.9 b/share/man/man9/vslock.9
index 5476271..badbf69 100644
--- a/share/man/man9/vslock.9
+++ b/share/man/man9/vslock.9
@@ -96,3 +96,9 @@ its per-process locked memory limit.
Some portion of the indicated address range is not allocated.
There was an error faulting/mapping a page.
.El
+.Sh BUGS
+The
+.Fn vslock
+function does not prevent memory from being unmapped out from underneath.
+This can lead to system instability and blocking conditions where they
+are required not to occur when accessing the locked memory.
OpenPOWER on IntegriCloud