From c9229237e9875723a8496691f165a3a325581758 Mon Sep 17 00:00:00 2001
From: mickey <mickey@openbsd.org>
Date: Fri, 21 Apr 2000 16:33:12 +0000
Subject: [PATCH] see if there is any meaning under curproc before using &proc0
 in vfs_syncwait(); from art@

---
 sys/kern/vfs_subr.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/sys/kern/vfs_subr.c b/sys/kern/vfs_subr.c
index 9a362e7f4bb..4b0c6178cbf 100644
--- a/sys/kern/vfs_subr.c
+++ b/sys/kern/vfs_subr.c
@@ -1,4 +1,4 @@
-/*	$OpenBSD: vfs_subr.c,v 1.43 1999/12/05 07:54:44 art Exp $	*/
+/*	$OpenBSD: vfs_subr.c,v 1.44 2000/04/21 16:33:12 mickey Exp $	*/
 /*	$NetBSD: vfs_subr.c,v 1.53 1996/04/22 01:39:13 christos Exp $	*/
 
 /*
@@ -1781,8 +1781,10 @@ vfs_syncwait(verbose)
 {
 	register struct buf *bp;
 	int iter, nbusy, dcount, s;
+	struct proc *p;
 
-	sys_sync(&proc0, (void *)0, (register_t *)0);
+	p = curproc? curproc : &proc0;
+	sys_sync(p, (void *)0, (register_t *)0);
  
 	/* Wait for sync to finish. */
 	dcount = 10000;
-- 
2.20.1