[src/trunk]: src/sys/ufs/lfs Make buildable again.

[toshii <toshii%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/245c665af4e6
branches:  trunk
changeset: 499353:245c665af4e6
user:      toshii <toshii%NetBSD.org@localhost>
date:      Sat Nov 18 02:11:23 2000 +0000

description:
Make buildable again.
The previous commit was a backout of rev. 1.45, which must be an accident.

diffstat:

 sys/ufs/lfs/lfs_vnops.c |  6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diffs (27 lines):

diff -r eeffab6fad3b -r 245c665af4e6 sys/ufs/lfs/lfs_vnops.c
--- a/sys/ufs/lfs/lfs_vnops.c   Sat Nov 18 02:08:30 2000 +0000
+++ b/sys/ufs/lfs/lfs_vnops.c   Sat Nov 18 02:11:23 2000 +0000
@@ -1,4 +1,4 @@
-/*     $NetBSD: lfs_vnops.c,v 1.48 2000/11/17 19:14:42 perseant Exp $  */
+/*     $NetBSD: lfs_vnops.c,v 1.49 2000/11/18 02:11:23 toshii Exp $    */
 
 /*-
  * Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
@@ -282,6 +282,8 @@
                struct vnode *a_vp;
                struct ucred *a_cred;
                int a_flags;
+               off_t offlo;
+               off_t offhi;
                struct proc *a_p;
        } */ *ap = v;
        
@@ -496,7 +498,7 @@
         * return.  But, that leaves this vnode in limbo, also not good.
         * Can this ever happen (barring hardware failure)?
         */
-       if ((error = VOP_FSYNC(*vpp, NOCRED, FSYNC_WAIT, curproc)) != 0) {
+       if ((error = VOP_FSYNC(*vpp, NOCRED, FSYNC_WAIT, 0, 0, curproc)) != 0) {
                printf("Couldn't fsync in mknod (ino %d)---what do I do?\n",
                       VTOI(*vpp)->i_number);
                return (error);