From d9b2500eeff7483f0219014c55beee1141daaf5d Mon Sep 17 00:00:00 2001
From: Brian Feldman <green@FreeBSD.org>
Date: Fri, 7 May 2004 11:43:24 +0000
Subject: [PATCH] In r1.190, vslock() and vsunlock() were bogusly made to do a
 "user wire" and a "system unwire."  Make this a "system wire" and "system
 unwire."

Reviewed by:	alc
---
 sys/vm/vm_glue.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys/vm/vm_glue.c b/sys/vm/vm_glue.c
index b8f284cb19a..b625615f935 100644
--- a/sys/vm/vm_glue.c
+++ b/sys/vm/vm_glue.c
@@ -216,7 +216,7 @@ vslock(void *addr, size_t len)
 		return (EAGAIN);
 #endif
 	error = vm_map_wire(&curproc->p_vmspace->vm_map, start, end,
-	    VM_MAP_WIRE_USER | VM_MAP_WIRE_NOHOLES);
+	    VM_MAP_WIRE_SYSTEM | VM_MAP_WIRE_NOHOLES);
 	/*
 	 * Return EFAULT on error to match copy{in,out}() behaviour
 	 * rather than returning ENOMEM like mlock() would.