summaryrefslogtreecommitdiffstats
path: root/share
diff options
context:
space:
mode:
authorgreen <green@FreeBSD.org>2004-08-16 03:12:10 +0000
committergreen <green@FreeBSD.org>2004-08-16 03:12:10 +0000
commit897f119a6f08a1b2be393d04b6aa43f1ae1fe697 (patch)
tree8fe14e5254f9a758ff7a9e066dc5aa078c0ee95f /share
parentd4f662585f29ddfad5c1b8e2b6ceb308fb8ae058 (diff)
downloadFreeBSD-src-897f119a6f08a1b2be393d04b6aa43f1ae1fe697.zip
FreeBSD-src-897f119a6f08a1b2be393d04b6aa43f1ae1fe697.tar.gz
Remove the BUGS entry for vslock(9) not actually holding user memory in place.
Diffstat (limited to 'share')
-rw-r--r--share/man/man9/vslock.96
1 files changed, 0 insertions, 6 deletions
diff --git a/share/man/man9/vslock.9 b/share/man/man9/vslock.9
index 72437fa..fdab0eb 100644
--- a/share/man/man9/vslock.9
+++ b/share/man/man9/vslock.9
@@ -96,9 +96,3 @@ 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