No need for uvm_useracc here now. vslock catches those problems.

1 files changed, 1 insertions, 16 deletions

diff --git a/sys/kern/kern_physio.c b/sys/kern/kern_physio.c
index bd83546c9dd..dc1b78fb8e2 100644
--- a/sys/kern/kern_physio.c
+++ b/sys/kern/kern_physio.c
@@ -1,4 +1,4 @@
-/*	$OpenBSD: kern_physio.c,v 1.17 2001/11/28 13:47:39 art Exp $	*/
+/*	$OpenBSD: kern_physio.c,v 1.18 2001/12/10 17:37:51 art Exp $	*/
 /*	$NetBSD: kern_physio.c,v 1.28 1997/05/19 10:43:28 pk Exp $	*/
 
 /*-
@@ -87,21 +87,6 @@ physio(strategy, bp, dev, flags, minphys, uio)
 	error = 0;
 	flags &= B_READ | B_WRITE;
 
-	/*
-	 * [check user read/write access to the data buffer]
-	 *
-	 * Check each iov one by one.  Note that we know if we're reading or
-	 * writing, so we ignore the uio's rw parameter.  Also note that if
-	 * we're doing a read, that's a *write* to user-space.
-	 */
-	if (uio->uio_segflg == UIO_USERSPACE)
-		for (i = 0; i < uio->uio_iovcnt; i++)
-			/* XXX - obsolete now that vslock can error? */
-			if (!uvm_useracc(uio->uio_iov[i].iov_base,
-			    uio->uio_iov[i].iov_len,
-			    (flags == B_READ) ? B_WRITE : B_READ))
-				return (EFAULT);
-
 	/* Make sure we have a buffer, creating one if necessary. */
 	if ((nobuf = (bp == NULL)) != 0)
 		bp = getphysbuf();