Remove the BUGS entry for vslock(9) not actually holding user memory in place.

This commit is contained in:
green 2004-08-16 03:12:10 +00:00
parent d4f662585f
commit 897f119a6f

View File

@ -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.